“How much will the app cost?” is the first question almost every founder asks us, and the honest answer is that it depends on decisions most people have not made yet. Two apps that both “let customers book appointments” can differ in cost by five times, depending on what happens behind the booking button.
This guide explains what actually drives the price, gives realistic ranges for the Indian market in 2026, and lists the costs that show up after launch.
What drives the cost
1. Scope: screens, features and user roles
The number of screens matters less than the number of distinct jobs the app does. Every new user role (customer, vendor, delivery partner, admin) adds its own flows, permissions and testing. A marketplace with three roles is close to three apps.
Features that consistently add cost:
- Real-time features: chat, live tracking, live inventory
- Payments with refunds, wallets, subscriptions or split payouts
- Offline mode and data syncing
- Video calling or streaming
- Complex search and filters
- Anything involving maps and routing
2. Platforms
You can build for Android only, iOS only, or both. In India, Android has the large majority of users, so many consumer apps launch on Android first. B2B and premium consumer apps usually need iOS from day one.
Cross-platform frameworks such as React Native and Flutter let one codebase serve both, typically saving 30 to 40% compared with building two separate native apps. We cover the trade-offs in a separate post comparing React Native, Flutter and native development.
3. Backend and admin panel
The app on the phone is often less than half the work. Behind it you need:
- A backend (API, database, business logic)
- An admin panel for your team to manage users, orders, content and support
- Authentication, notifications and file storage
- Reporting and exports
Using a managed backend such as Firebase or Supabase reduces the initial cost for simpler apps. Apps with complex business rules usually need a custom backend.
4. Design
Using a well-built component library with your brand colours costs far less than custom illustration, animation and a fully bespoke design system. Good UX research and clickable prototypes add cost up front but reduce expensive rework during development.
5. Integrations
Each third-party service adds setup, testing and error handling: payment gateways (Razorpay, Cashfree, PayU), SMS and WhatsApp OTP, shipping (Shiprocket, Delhivery), accounting (Tally, Zoho Books), CRMs, Aadhaar or KYC verification, and ERP systems. A legacy system without a clean API can take more time than the rest of the app combined.
6. Quality assurance
Testing on a range of real Android devices (including mid-range and older phones, which many of your users will have), plus iPhones, takes real time. Budget around 15 to 25% of development effort for QA. Apps that handle payments or health data need more.
7. Who builds it
Rates vary widely between freelancers, small studios and large firms. A lower hourly rate does not always mean a lower total: inexperienced teams often take longer and leave code that is expensive to change. Ask who will actually work on your project and whether they have shipped similar apps.
Realistic ranges for India in 2026
These are typical ranges for a professional team in India building both Android and iOS with a cross-platform framework, including design, backend, admin panel and QA. They are a starting point for budgeting, not a quote.
| App type | Examples | Typical range (INR) | Typical timeline |
|---|---|---|---|
| Simple MVP | Lead capture, catalogue, booking with basic admin | 3 to 8 lakh | 6 to 10 weeks |
| Business app | Clinic booking with payments, loyalty app, field sales app | 8 to 20 lakh | 3 to 5 months |
| E-commerce or D2C app | Catalogue, cart, payments, order tracking, offers | 10 to 25 lakh | 3 to 6 months |
| Marketplace or on-demand | Customer, vendor and delivery apps with live tracking | 25 to 60 lakh | 6 to 9 months |
| Complex platforms | Fintech, telemedicine, large enterprise systems | 50 lakh and above | 9 months and more |
Building separate native apps for Android and iOS usually pushes these figures up. Highly regulated products (lending, insurance, health records) also need security reviews and compliance work that add to the total.
Hidden and ongoing costs
Many budgets stop at launch day. These are the costs that follow.
Store fees
- Apple Developer Program: US$99 per year, charged in local currency, required to publish on the App Store.
- Google Play Console: a one-time US$25 registration fee.
- In-app purchase commission: if you sell digital goods or subscriptions inside the app, Apple and Google take a commission, commonly 15% or 30% depending on the programme. Physical goods and real-world services (food, products, appointments) are paid through your own gateway instead.
Hosting and third-party services
Expect monthly costs for cloud hosting, databases, file storage, push notifications, SMS or WhatsApp OTPs, maps API usage, email, error monitoring and analytics. For a small app this may be a few thousand rupees a month. For an app with real traffic, video or heavy maps usage it can run into lakhs. Ask your developer for a monthly estimate at 1,000, 10,000 and 1,00,000 users.
Payment gateway charges
Gateways charge a fee per transaction that varies by payment method and plan. Build this into your pricing, not just your tech budget.
Maintenance
Plan for 15 to 20% of the original build cost every year. This covers:
- Updates for new Android and iOS versions. Google Play requires apps to target a recent Android API level each year, and Apple periodically requires builds with newer Xcode and SDK versions.
- Updating libraries and fixing security issues
- Bug fixes from real-world use
- Server monitoring and backups
An app that is not maintained will eventually be hidden from new users in the stores or stop working on new phones.
New features
Once real users arrive, you will want changes. Keep part of your budget for a second version based on what users actually do.
How to cut cost with an MVP
A minimum viable product is the smallest version of the app that lets real users complete the core job and lets you learn whether the idea works. Done well, it can bring a 20 lakh plan down to 6 or 8 lakh.
- Write down the one core journey. For a clinic app, it might be “find a doctor, book a slot, pay, get a reminder”. Everything else waits.
- List every feature and label it must, should or later. Be strict. Chat, referral programmes, wallets and multiple languages are usually “later”.
- Use one cross-platform codebase, or launch on Android first if your users are mainly Android.
- Use managed services for login, notifications and payments rather than building your own.
- Keep the admin panel simple. Your team can live with plain tables for the first few months.
- Consider a web app first. If your users do not need the camera, offline access or frequent push notifications, a fast mobile website or progressive web app may test the idea for much less.
- Agree on a fixed scope for version one and a separate backlog for version two, so new ideas do not quietly extend the timeline.
Questions to ask before you sign
- Is the quote fixed price or time and materials, and what happens when scope changes?
- Does it include the backend, admin panel, QA and store submission?
- Who owns the source code and the cloud accounts? (It should be you.)
- What does the maintenance contract cover after launch, and what does it cost?
- Can I see two apps you have shipped that are still live in the stores?
If you have an app idea and want a budget range before talking to developers, our instant quote tool gives you an estimate based on the features you choose.