PRD Template for Mobile App

Example: "42% of our daily active users access our web application from mobile browsers, but the experience is poor — key actions require horizontal scrolling, touch targets are too small, and the data-heavy dashboard is unusable on small screens. Mobile browser users have a 60% lower task completion rate and a 45% higher bounce rate than desktop users. In user interviews, 28 of 35 users said they would use a mobile app for quick checks and approvals but continue using desktop for deep work."

Example: "Primary: Support 3 key mobile use cases (quick status checks, approvals, and capture via camera) with a task completion rate above 90%. Adoption: 30% of active users install the mobile app within 6 months of launch. Engagement: Users who install the mobile app increase their weekly active days by 40%. Performance: App launch to usable content in under 2 seconds. App store rating: 4.5+ stars maintained."

Example: "As a PM on the go, I want to approve or reject a pending request from a push notification so that I do not block my team while I am away from my desk. Acceptance criteria: push notification shows request summary and action buttons; tapping 'Approve' or 'Reject' completes the action without opening the app; if more context is needed, tapping the notification opens the full request in the app; the action is reflected in the web app within 5 seconds."

Example: "FR-1: The app must support iOS 16+ and Android 12+ (covering 95%+ of active devices). FR-2: Navigation must use native patterns: tab bar on iOS, bottom navigation on Android. FR-3: The app must support offline access for recently viewed data, synced when connectivity returns. FR-4: Push notifications must support actionable buttons (approve/reject) without opening the app. FR-5: Authentication must support biometrics (Face ID, fingerprint) for returning users. FR-6: The app must support deep linking from web URLs and shared links."

Example: "NFR-1: Cold launch to interactive content must be under 2 seconds on mid-range devices. NFR-2: The app must not consume more than 3% of battery per hour of active use. NFR-3: Initial app download size must be under 25MB. NFR-4: The app must function on 3G connections with graceful degradation. NFR-5: Background data sync must not exceed 10MB per day. NFR-6: The app must support screen readers (VoiceOver on iOS, TalkBack on Android)."

Example: "Metric 1: Mobile app adoption (installs / active users). Target: 30% within 6 months. Metric 2: Weekly active days for users with mobile app vs. without. Target: 40% higher with mobile. Metric 3: Mobile task completion rate. Target: 90%+ for core use cases. Metric 4: App store rating. Target: 4.5+ stars. Metric 5: Crash-free session rate. Target: 99.5%+."

Example: "We will use React Native (with Expo) to share 80%+ of code between iOS and Android, reducing development effort by ~40% compared to separate native apps. Our existing React web team can contribute to the mobile codebase with minimal ramp-up. Platform-specific code will be used for biometric authentication, push notification handling, and camera integration. State management will use the same TanStack Query patterns as our web app, sharing API client code. Offline data will be stored in SQLite via a background sync queue."

Example: "Risk: App store rejection due to guideline violations (Apple is especially strict about web-view wrappers and subscription pricing). Likelihood: Medium. Impact: High (delays launch by 1-4 weeks per rejection). Mitigation: Review Apple and Google guidelines before design. Use native navigation and platform-specific UI patterns. Submit for review 2 weeks before planned launch. Risk: React Native performance is insufficient for data-heavy screens. Likelihood: Medium. Impact: Medium. Mitigation: Profile performance on mid-range Android devices early. Use native modules for performance-critical screens."