The mobile app development process has eight stages: discovery, wireframes, UI design, MVP scoping, development in sprints, testing, store submission and post-launch updates. A focused first version usually takes three to six months from the first meeting to going live on the Play Store and App Store. Most delays come from the client side, not the code, so knowing what you need to provide at each step saves weeks.
Below is how each stage works, what you should get from your developer, and what they will need from you.
Why the mobile app development process matters more than the tech stack
Most business owners start by asking “Flutter or native?” That question matters, but less than people think. In our experience, apps fail more often because the wrong thing was built, the scope kept changing, or nobody planned for what happens after launch.
A clear process protects you. It forces decisions early, when they are cheap, instead of in month four, when changing a screen means rewriting code that five other screens depend on. When you talk to a freelancer or an app development company in Kolkata, ask them to walk you through their process first, then talk about price.
Planning: discovery, wireframes and design
Step 1: Discovery (1 to 3 weeks)
Discovery answers three questions: who will use the app, what problem it solves for them, and how the business makes money or saves money from it.
For a coaching institute, that might be: students need recorded lectures and test series on their phone; parents want attendance and results; the institute wants fewer WhatsApp groups and paid course sales.
What you should get: a written scope document with user types, a feature list split into “must have” and “later”, the platforms (Android, iOS or both), integrations needed (payment gateway, SMS, maps, existing software) and a rough timeline.
What you must provide: access to the people who understand the business, examples of apps you like and why, any existing systems the app must talk to, and a decision-maker who can answer questions within a day or two.
Step 2: Wireframes and user flows (1 to 2 weeks)
Wireframes are plain black-and-white screen layouts. They show what goes on each screen and how a user moves from one to the next: open app, log in with OTP, browse, add to cart, pay, track order.
This is the cheapest place to make changes. Moving a button in a wireframe takes minutes. Moving it after development can take days.
What you must provide: honest feedback. Click through every flow as if you were a customer. If something feels confusing now, it will be worse on a small phone in a moving auto.
Step 3: UI design (2 to 4 weeks)
Now the wireframes get colors, fonts, icons and real content. Good UI design follows platform conventions: Android users expect certain navigation patterns and iPhone users expect others. A clickable prototype lets you test the app on your own phone before any code is written.
Expect a small design system as part of this: buttons, form fields, colors and spacing rules, so every new screen looks consistent. Our UI/UX design team works this way, and our post on how UI/UX design affects conversions explains why it is worth the time.
What you must provide: logo files, brand colors, real product photos or content, and app text in every language you plan to support.
Step 4: Locking the MVP scope
MVP means minimum viable product: the smallest version that real users will pay for or actually use. This is where most projects either stay on track or go off the rails.
A simple test for each feature: “Will a user complain on day one if this is missing?” If not, it waits for version two. A food ordering app needs a menu, cart, payment and order tracking at launch. Loyalty points, referral codes and scheduled orders can follow.
Write the final scope down and sign it off. Changes after this point are normal, but each one should be added to a list with its cost and time impact, not slipped in quietly.
Building and testing the app
Step 5: Development in sprints (6 to 14 weeks)
Development usually runs in two-week sprints. Each sprint delivers a working set of features you can test on your phone, not just a progress report.
A typical app has three parts built in parallel:
- The mobile app for Android and iOS, built natively (Kotlin, Swift) or cross-platform (Flutter, React Native)
- The backend and APIs that store data, handle logins and run business logic
- An admin panel where your staff manage products, users, orders or content
Integrations come in here: payment gateways like Razorpay, maps, SMS and WhatsApp notifications, push notifications, and any existing ERP or billing software. If you need features like Apple Pay or HealthKit, the native route has advantages, which we covered in our guide to native iOS app development.
What you must provide: someone who tests each sprint build within a few days and reports issues clearly, with screenshots. Silence for three weeks followed by twenty change requests is the most common cause of delays we see.
Step 6: Testing and QA (2 to 3 weeks, plus ongoing)
Testing happens throughout development, but the final round before launch is the most thorough. It should cover:
- Functional testing: every flow, every button, every error message
- Device testing: low-end Android phones, older iPhones, small and large screens
- Network testing: slow 4G, switching between Wi-Fi and mobile data, offline behavior
- Payment testing: success, failure, refunds and duplicate taps
- Security basics: data stored safely on the device, APIs that check who is calling them
In India, testing on budget Android phones is not optional. Many of your users will be on budget phones with limited memory, and an app that runs smoothly on the developer’s flagship can stutter badly on them.
Launching on the Play Store and App Store
Step 7: Store submission (1 to 3 weeks)
Store submission has more steps than most people expect, so start the paperwork early.
| Item | Google Play | Apple App Store |
|---|---|---|
| Developer account fee | US$25 one-time | US$99 per year |
| Account verification | ID verification; organizations need business details | D-U-N-S number for organizations |
| Testing before launch | New personal accounts need a closed test with 12 testers for 14 days | TestFlight is optional |
| Review | Usually a few days for new apps | Usually one to a few days, can be longer if rejected |
| Required listings | Privacy policy, Data safety form, screenshots, content rating | Privacy policy, privacy labels, screenshots, review notes and demo login |
The Play testing rule catches many first-time founders. According to Google’s Play Console help page, personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. We usually advise businesses to register an organization account instead, which also looks more trustworthy on the store listing.
Apple reviews every app against its App Store guidelines. Common rejection reasons are missing demo login details, broken links, incomplete features and apps that are just a website in a wrapper.
What you must provide: your developer accounts (in your company’s name, never the agency’s), privacy policy, app description, screenshots approval and a test account for Apple’s reviewers.
Step 8: Launch and post-launch updates
Going live is the start, not the end. The first month usually brings crash reports from devices nobody tested, user feedback you did not expect and small fixes.
Plan for:
- Crash and analytics monitoring from day one (Firebase Crashlytics and Analytics are common choices)
- A bug-fix window of four to eight weeks after launch, usually included in the project
- OS updates: Apple and Google release new versions every year, and Google Play requires apps to target a recent Android API level to keep publishing updates
- Version two planning, based on what users actually do, not what you guessed in discovery
A maintenance plan after the warranty period is normal. Budget something every year for updates, hosting and small improvements.
Realistic timeline at a glance
| Stage | Simple app | Medium app (MVP with admin panel) |
|---|---|---|
| Discovery | 1 week | 2 to 3 weeks |
| Wireframes and UI design | 2 to 3 weeks | 4 to 6 weeks |
| Development | 6 to 8 weeks | 10 to 14 weeks |
| Testing | 1 to 2 weeks | 2 to 3 weeks |
| Store submission | 1 week | 1 to 3 weeks |
| Total | about 2.5 to 3.5 months | about 4.5 to 6 months |
Stages overlap a little in practice, so totals can come in slightly shorter. Large apps with multiple user types, like a delivery app with customer, rider and restaurant apps, take longer.
Frequently asked questions
How long does it take to develop a mobile app?
A simple app with a handful of screens takes around two and a half to three and a half months. A typical MVP with a backend and admin panel takes four and a half to six months. Complex multi-app platforms can take longer.
What do I need before contacting an app developer in Kolkata?
A clear description of who the app is for and what it must do on day one, a few example apps you like, and a rough budget. You do not need wireframes or technical documents. A good app developer in Kolkata will help you create those during discovery.
Should I build for Android and iOS at the same time?
If your users are mostly in India, Android alone is often enough for the first version, since most Indian smartphone users are on Android. If you are targeting premium customers or international markets, launch both. Cross-platform frameworks like Flutter make building both together more affordable.
Who should own the developer accounts and source code?
You should. Register the Google Play and Apple developer accounts in your company’s name and add the agency as a user. Make sure your contract gives you full ownership of the source code and access to the repository.
How do I develop an app without technical knowledge?
You do not need to code. Your job in the process is to know your users and business well, make decisions quickly, and test each build honestly. Choose a team that explains each stage in plain language and shows you working builds every two weeks.
Planning an app?
If you have an idea and want to understand the realistic scope, timeline and process for your business, see our mobile app development services or contact us. As a mobile app development company in Kolkata, we are happy to walk you through how your app would move from idea to launch.
