Shipping a mobile app MVP in 12 weeks: what to build and what to skip

Founders often ask for everything in version one. The apps that succeed usually launch with far less and learn faster.

Weeks 1–2: decide what the MVP must prove

• Write down the one behaviour you need users to repeat
• Cut every feature that does not support that behaviour
• Agree on two or three numbers that define success

Weeks 3–4: design the core flow

Clickable prototypes in Figma, tested with five real users. Fixing a screen here costs hours; fixing it after launch costs weeks.

Weeks 5–10: build in two-week sprints

• One cross-platform codebase (React Native or Flutter) for iOS and Android
• A managed backend so the team spends time on the product, not servers
• A demo build every sprint so stakeholders see progress, not status reports

Weeks 11–12: harden and launch

Crash reporting, analytics, store listings and a beta on TestFlight and Play Console before the public release.

What to skip in version one

• Complex admin panels (a spreadsheet or simple dashboard will do)
• Offline sync, unless it is the product
• Multiple user roles and fine-grained permissions

Planning an app? Tell us the idea and we will help you trim it to an MVP.