Phase 1 — Discovery: scope locks in writing
Discovery runs 1–2 weeks; user personas, screen map, priority list, and tech selection are clarified. The phase ends with a written fixed-scope quote.
Without discipline, scope creep slows every sprint. The written quote locks scope; any change is added as a change request.
Phases 2 and 3 — Design and development run in parallel
Design runs 1–2 weeks; Figma component-based system and clickable prototype emerge. Development runs 4–8 weeks via weekly demos and sprint reviews.
Design and development are parallel. The next screen's design progresses while the previous one's development implements. The parallelism doubles delivery speed.
Phase 4 — The real process starts after launch
App Store + Play Store launch is a technical checklist; the real challenge starts after launch. Monthly support packages turn bug fixes, performance monitoring, and small features into a steady process.
30 days post-launch is data collection: activation, retention, conversion. From month 2 these signals shape the change-request flow.
Related services
Related articles
Other articles that support the same decision
Cost Analysis
Mobile App Cost in 2026: What Actually Sets the Price?
A clear breakdown of the product and engineering decisions that make mobile app proposals diverge in price.
City Guide
Working With a Mobile App Team in Istanbul: Remote or Hybrid?
A practical look at delivery rhythm and communication when working with Istanbul-based product teams.
Technology Choice
Flutter or React Native? A Business-First Decision Guide
A practical comparison based on team model, performance target, and product roadmap rather than framework hype.
Next step
If you are planning a similar project, we can clarify the scope and shape the right proposal flow together.
Start a project request