Mobile App MVP Checklist: 12 Things to Define Before Writing Code

Most mobile apps don't fail because the code is bad. They fail because decisions that should have been made before sprint 1 get deferred until sprint 6 — at which point they're expensive to reverse and impossible to ignore.

This checklist covers the 12 things every founder or product manager should be able to answer before a development team writes a single line of code.

Product definition

• 1. Who is the primary user? Not 'everyone' — one specific person with a specific problem.
• 2. What is the single core action the app enables? If you can't describe it in one sentence, the scope is too broad.
• 3. What does success look like at 90 days post-launch? (Downloads, revenue, retention rate — pick one primary metric.)
• 4. What are the 3 screens users will visit every session? Everything else is secondary.

Technical decisions

• 5. iOS, Android, or both? Starting with both doubles cost and timeline. What does your target user actually use?
• 6. Do you need a backend? If users have accounts, sync data, or communicate — yes. Many MVPs can start with a BaaS (Firebase, Supabase) instead of custom infrastructure.
• 7. What third-party integrations are required on day one vs. nice-to-have? Stripe, push notifications, and analytics each add time.
• 8. Do you have an existing API or backend the app needs to connect to? If yes, is the documentation current?

Business & legal

• 9. Do you have an Apple Developer account? ($99/year, takes 24–48h to activate — don't start development without one.)
• 10. Does your app handle health data, payments, or user-generated content? Each has specific App Store review requirements you need to design around.
• 11. Who owns the IP? Founders, company, or investors? This affects your contract with any development partner.
• 12. What's your post-launch maintenance plan? iOS and Android release major OS updates annually — plan for at least one maintenance cycle per year.

The two questions that matter most

Of all twelve, two questions derail more projects than the rest combined:

Who is the decision-maker? Every agency needs one person who can approve designs, unblock questions, and sign off on scope decisions within 24 hours. Committees kill timelines. If that person isn't identified before kickoff, identify them now.

What's not in the MVP? Every feature you cut before development starts saves 3–5× more than cutting it mid-sprint. Make an explicit "not now" list and get stakeholder alignment on it before the first line of code.

What to do with this list

Go through each item and write a one-paragraph answer. Share it with your development partner before the first call. You'll cover more ground in 30 minutes than most teams cover in three kickoff meetings — and you'll get a more accurate estimate as a result.