Service · mobile app development company

Mobile app development

An MVP with 8–12 core screens usually takes 10–16 weeks from kickoff to store approval. A larger app with payments, real-time features and an admin panel usually takes 5–8 months.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Hiring a mobile app development company is a bet on the team that will still be fixing, shipping and scaling the app a year after launch. Red Balloon builds iOS, Android and cross-platform apps for D2C brands, clinics, logistics operators, lenders and startups across India, with app developers in Gurgaon and New Delhi working alongside your product owner. We start with the business case, the journeys that matter and the metric the app must move, then pick native, Flutter or React Native to suit it. Analytics, crash alerts and release automation are set up from the first build. App development cost in India depends on platforms, integrations and backend work, so we scope it in writing first.

Where this works

Real-world situations we're built for

Illustrative · not a client
D2C / ecommerce

Gurugram skincare brand on Shopify; most traffic is mobile web and buyers rarely reorder after a first COD order

What we'd do
Flutter app on Shopify APIs with UPI checkout, order tracking and WhatsApp-linked reorder reminders
What moves
Repeat purchase rate up, prepaid share up, RTO rate down
Healthcare

Delhi multi-specialty clinic chain books appointments by phone; reception overloaded, no-shows high

What we'd do
Patient app with slot booking, UPI prepayment, reminders and lab report download, integrated with the existing hospital system
What moves
No-show rate down, online booking share up, inbound calls down; tracked as no-show rate before and after, over a fixed period
Logistics

Noida last-mile operator uses paper proof of delivery; disputes take days to settle

What we'd do
Offline-first rider app for budget Android phones with photo POD, OTP handover and GPS trail synced when network returns
What moves
Dispute resolution time down, POD capture rate up, failed deliveries down
How a project runs

5 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Discovery

1–2 weeks

Stakeholder and user interviews, feature list, integration audit, platform and stack decision

You get: Scope document, prioritised backlog, estimate

We need: Decision-maker time, access to existing systems, a few real users

UX/UI design

2–4 weeks

User flows, wireframes, Figma prototype, usability test, design system

You get: Approved Figma screens and prototype

We need: Brand assets, feedback within 48 hours

Build

6–16 weeks

Two-week sprints covering APIs, app screens, admin panel, analytics events and CI builds

You get: Test builds and a demo every sprint

We need: Product owner at sprint reviews, third-party API credentials

QA and release

2–3 weeks

Real-device testing, security checks, store listings, privacy forms, closed testing; rule of thumb: start Play staged rollout at 10% and widen after 48 hours without a new top crash

You get: Store-approved apps and release notes

We need: Developer accounts in your company name, legal pages, store copy

Support and iterate

Ongoing, monthly

Crash fixes, OS and SDK updates, feature sprints driven by analytics

You get: Monthly release and app health report

We need: Priorities and feedback from your support team

A typical engagement

From first call to result

Illustrative · not a client

Gurugram home-services startup, 40 staff, seed-funded, bookings via WhatsApp and a Google Form, Razorpay payment links, Google Sheets for scheduling

Weeks 1–2DiscoveryMap the booking journey, interview 8 customers and 5 technicians, list integrations: Razorpay, Google Maps, WhatsApp BSPScope signed: customer app, technician app, admin panel; Flutter for both platforms
Weeks 2–5UX and UI designFigma prototype of booking, slot choice, payment and tracking, tested with 5 users on budget Android phonesApproved screens and component library
Weeks 3–9Backend and adminAPIs for slots, pricing and technician assignment; ops admin panel; Razorpay UPI and cards with verified webhooksStaging API and admin panel used by ops
Weeks 5–11App buildTwo-week sprints on both Flutter apps, push via Firebase Cloud Messaging, analytics event plan implementedTestFlight and Play internal builds every sprint
Weeks 10–13QA and closed testTesting on a 3 GB RAM Android phone and iPhones, Play closed test with the Play Console pre-launch report, refund edge cases, OWASP MASVS checksRelease candidate with crash data from Crashlytics
Weeks 13–14Store launchStore listings, Play Data safety form, Apple privacy labels, phased rollout; most common delay: a reviewer demo login that has expired or needs an OTPBoth apps live on App Store and Google Play
Weeks 15–20Stabilise and growFix top crashes, add rebooking nudges, move WhatsApp customers into the app with deep linksPrioritised backlog for next quarter
Where it starts1,800 bookings/month, 70% arriving as WhatsApp chats, 12% cancellations, no customer app, technicians coordinated by phone
Where it endsCustomer app, technician app and admin panel in the client's own accounts. Weekly watch: share of bookings via app, crash-free users, repeat booking rate.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Crash-free usersUsers with no crash ÷ total users, per dayRule of thumb: hold above 99% crash-free users on every release; pause the staged rollout if a new version dips below itFirebase CrashlyticsDaily after a release, weekly otherwise
User-perceived crash rate (Android)Daily users with a user-perceived crash ÷ daily active usersBelow Google Play's published bad-behaviour threshold of 1.09%Play Console Android vitalsWeekly
User-perceived ANR rate (Android)Daily users with a user-perceived 'app not responding' ÷ daily active usersBelow Google Play's published bad-behaviour threshold of 0.47%Play Console Android vitalsWeekly
Day-7 and day-30 retentionUsers active on day N ÷ users who installed on day 0, per cohortSet from your first cohorts, then aim for steady quarter-on-quarter improvementFirebase Analytics, Mixpanel or Amplitude cohortsMonthly
Activation rateNew users completing the key action (first booking, first order) ÷ installsSet from launch baseline, then raise it through onboarding A/B testsGA4 for Firebase, Mixpanel or Amplitude funnelsWeekly
Cold start timeTap to first usable screen, p90, on a budget Android reference phoneWell under the 5 s cold start Android vitals treats as excessive; rule of thumb: under 2 s at p90 on the reference phoneFirebase Performance Monitoring, Android vitals startup reportEvery release
Store ratingAverage rating over the last 90 days plus count of reviews mentioning bugsRule of thumb: 4.0 stars or higher over 90 days; reply to every 1–2 star review within two working daysApp Store Connect, Play ConsoleWeekly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Every merge to mainBuild, sign and upload test buildsGitHub Actions with Fastlane to TestFlight and the Play internal trackRemoves: Hours of manual builds and signing mistakes each sprint
When: Crash spike after a releaseCrash alertingCrashlytics velocity alerts routed to Slack or emailRemoves: A bad release staying live for days
When: Every pull requestAutomated UI testsFlutter integration_test, Detox or Maestro running on Firebase Test Lab devicesRemoves: Regressions on screens nobody manually rechecked
When: Weekly scheduleDependency and SDK updatesDependabot or Renovate pull requests checked by CIRemoves: Missing store target-SDK deadlines and shipping known vulnerabilities
When: New review under 3 starsReview monitoringApp Store Connect and Play Console APIs feeding Zendesk, Freshdesk or a Slack channelRemoves: Unanswered negative reviews dragging ratings down
Rules we work to

Standards and regulations

AppleApp Store Review Guidelines

Decide approval: in-app purchase rules, privacy disclosures, account deletion, minimum functionality; each rejection adds a review cycle

GoogleGoogle Play Developer Program Policies

Data safety form, target API level, permission declarations and testing rules must be met before and after launch

OWASPOWASP MASVS and MASTG

Mobile security requirements and test guide: storage, network, authentication, resilience; used for pre-release security checks

MeitYDPDP Act 2023 and DPDP Rules 2025

From 13 May 2027, consent notices, purpose limits, security safeguards, breach reporting and deletion rights apply to personal data the app collects

What's changing

Platform and policy updates that affect this work

We track: Apple Developer News and Updates, Android Developers Blog, Play Console Help: policy announcements, MeitY notifications.

AppleEnforcement began for privacy manifests: apps and SDKs using 'required reason' APIs must declare why

Every third-party SDK in your app needs a current privacy manifest or uploads are rejected

Google PlayClosed-test requirement for new personal developer accounts cut from 20 to 12 testers for 14 days

Plan the closed test early, or publish from an organisation account

AppleUploads to App Store Connect must be built with Xcode 16 and the iOS 18 SDK

Apps not updated recently need a rebuild and retest before their next release

MeitYDPDP Rules 2025 notified; main duties apply from 13 May 2027

Consent flows, retention limits and breach response should be designed into apps now

Before you hire anyone

Questions to ask any agency, including us

Can we speak to a client whose app you still maintain a year after launch?

Why ask

Launch is the easy part; upkeep through OS and SDK changes shows real capability

A good answer

A reference, release history, and how they handled a forced SDK or store policy change

Which physical devices will you test on, including low-end Android?

Why ask

Most Indian users are on mid-range and budget Android phones that emulators don't represent

A good answer

A named device list by RAM tier and Android version, plus a cloud device lab for the rest

Who writes the code day to day, and will that team stay for the whole project?

Why ask

Swapping developers mid-build loses context and slows delivery

A good answer

Named roles, seniority, allocation percentage and a handover plan if someone leaves

How do you report progress, and what happens when scope changes?

Why ask

Unclear change control is a leading cause of budget overruns

A good answer

Sprint demos, a shared board, and written change requests with effort and cost before work starts

What does post-launch support include?

Why ask

Apps need yearly updates for new OS versions and store rules

A good answer

A defined SLA, response times, monthly scope and a price quoted after scoping

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Flutter, React Native or native: which should we choose?

For most business apps we use Flutter or React Native, which gives you one codebase and one team for iOS and Android. We recommend native Swift and Kotlin when the app depends heavily on device hardware, background processing or platform-only features.

  • Flutter (Dart) draws its own UI, so screens look the same on a ₹10,000 Android phone and an iPhone. It's a good default for design-heavy consumer apps.
  • React Native (TypeScript) has used its New Architecture by default since version 0.76. It's the better choice if your web product is React or Next.js and you want to share logic and developers.
  • Native is the right call for heavy Bluetooth LE work (medical devices, wearables), AR, continuous background location, widgets, HealthKit or CarPlay.
  • Android has well over 90% of India's smartphone market, so we test performance on budget Android hardware first.
How much does app development cost in India?

A production-ready MVP from Red Balloon is quoted after scoping. The price depends mainly on the number of user roles, integrations and real-time features, more than on screen count.

  • What raises cost: each extra user role (customer, partner, admin), payments (Razorpay, Cashfree, UPI intent), real-time features (chat, live tracking), offline mode, and ERP or CRM integrations.
  • Fixed platform fees: Apple Developer Program US$99 a year; Google Play US$25 one-time.
  • Running costs: hosting, push notifications, SMS or WhatsApp OTP, maps API calls, and maintenance. Budget about 15–20% of the build cost each year for updates, because Apple and Google change OS and SDK requirements every year.
  • We give a line-item estimate after the paid discovery workshop, not from a single call.
Who owns the source code, app store accounts and data?

You own all of it from day one. The code lives in your GitHub or GitLab organisation, the App Store and Play Console accounts are in your company's name, and cloud billing is on your card.

  • The contract assigns IP to you on payment. We work as members in your accounts, not owners.
  • Play App Signing holds the app signing key, so you never depend on one developer's laptop for updates.
  • Handover checklist: repositories, CI/CD pipelines (GitHub Actions, Codemagic or Fastlane), environment secrets in your vault, architecture document, and admin access to every third-party service.
How do you handle security and personal data under India's DPDP Act?

We collect only the data each feature needs, record consent with its purpose and timestamp, encrypt data in transit and at rest, and build data access and deletion requests into the app from the start.

  • The DPDP Rules were notified on 13 November 2025, and the Act's main duties (notice, consent, security, breach reporting) apply from 13 May 2027. Apps launching now should be built to comply from day one.
  • We test security against OWASP MASVS: tokens in Keychain or Keystore, no secrets in the app bundle, and certificate pinning for health and finance apps.
  • We complete the store disclosures with you: Google Play's Data safety form, and Apple's privacy labels and privacy manifest.
Back to the practice

Product Engineering →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.