Twelve weeks is enough time to take a well-scoped mobile product from a whiteboard to real users on the App Store and Google Play. It isn't enough to build everything. The goal of an MVP is to learn, with real users, whether the core idea works.
Here's the plan we use, adapted to each project.
Weeks 1–2: Discover and decide
- Workshops with the business owner, operations and a few target users.
- Process mapping: how the work happens today, and where the friction is.
- One success metric for the MVP, such as bookings completed, orders placed or time saved.
- Scope: a prioritised backlog with a firm line between "MVP" and "later".
- Tech decisions: stack (see Flutter or native?), back end, integrations and hosting.
The output is a clear scope and a fixed estimate for the build.
Weeks 3–4: Design and prototype
- User journeys for the three to five core flows.
- Wireframes, then high-fidelity designs on a small design system.
- A clickable prototype tested with five to eight real users. This catches most usability problems before any code is written.
Weeks 5–10: Build in two-week sprints
Three sprints, each ending with a demo on real devices:
- Sprint 1: sign-up and sign-in, core data model, the main flow working end to end (even if rough).
- Sprint 2: payments or integrations, notifications, admin tools for your team.
- Sprint 3: polish, edge cases, analytics, accessibility and performance.
Throughout, automated tests and a staging build mean you can try every change on your own phone within a day.
Week 11: Harden
- Testing across devices, including the older Android phones many Malaysian users still carry.
- Security review: authentication, data storage, API protection.
- A PDPA check on what personal data is collected, why and for how long.
- Store listings, screenshots and privacy labels.
Week 12: Launch
- Submit to the App Store and Google Play. Allow time for review, especially for a first release.
- Soft launch to a limited group, with monitoring and crash reporting live.
- A launch-week support rota so issues are fixed within hours.
After launch: learn, then add AI
The MVP's real job starts at launch. Use the first month of analytics and feedback to plan version 2. That's also when AI features make the most sense: once you have real usage data, you can add search, recommendations or an assistant based on what users actually do. Our article on AI features for existing apps covers the options.
What makes 12 weeks possible
- A decision-maker on the client side who's available every week.
- Scope discipline: new ideas go to the "later" list, not into the sprint.
- Reusing proven building blocks, such as our payment, eKYC and IoT platforms, instead of rebuilding them.
Have an app idea?
Book a free one-hour scoping session. You'll leave with a clearer MVP scope and a realistic timeline. Book a scoping session →
