Specialist service · android app development company

Android app development

We usually set minSdk 24–26, target the API level Google Play currently requires, and test on budget 3–4 GB RAM phones from Xiaomi, Samsung's Galaxy M and A series and realme alongside a flagship.

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

Most of your Indian users are on Android, many on budget phones with limited memory and patchy networks, and a good Android app development company builds for those phones first. Red Balloon develops native Android apps in Kotlin for field sales teams, distributors, agritech firms, lenders and consumer brands. We design offline-first flows where connectivity drops, keep app size and battery use low, and test on the handsets your customers actually carry. Releases move through internal and closed testing tracks before production, and Android vitals are watched closely after launch. Android app development cost depends on screens, offline needs, device integrations such as scanners or GPS, and backend work, and the Play Console account belongs to you.

What drives Android app development cost

Android app development cost rises with the number of screens and user roles, how much must work offline, and which device features the app uses, such as barcode scanning, GPS tracking, the camera or Bluetooth printers. The width of the device range matters too: supporting older Android versions and many budget models adds testing time. Backend work is often the hidden part, because an app is only as good as the APIs and admin tools behind it.

As an Android app development company in India, we scope these items one by one during the Growth Audit and quote a fixed first release. Integrations with Tally, an ERP or a payment gateway are priced separately, so you can see what each one adds and decide what belongs in version one.

Keeping an Android app current, year after year

An Android app is never finished in the way a brochure is. Google Play raises its target API level requirement every year, and an app that misses it stops reaching new users and eventually cannot ship updates. Libraries and SDKs go out of date, phone makers change battery and background rules, and new Android versions change how notifications, permissions and layouts behave.

We plan for this from the start. Each year's target API change goes into the roadmap months ahead, dependencies are updated on a regular schedule rather than in a rush, and release notes from Google are tracked by the team. Budgeting a steady amount of upkeep each quarter costs less than one emergency rebuild after a missed deadline.

Getting installs and keeping users once the app is live

Consumer apps need a plan for installs as well as code. Our Performance Marketing team runs Google App campaigns and Meta app install ads, with Firebase or an attribution tool such as AppsFlyer measuring which campaigns bring users who stay. The Search & Content team writes the Play Store listing, screenshots and descriptions for the searches your users actually make, in English and Indian languages.

For field and distributor apps the focus is adoption instead: short training videos, a simple first-run flow and usage reports by branch. The AI & Automation practice often connects the app's data to WhatsApp alerts or reports for managers, so the app becomes part of daily work rather than one more login.

Where this works

Real-world situations we're built for

Illustrative · not a client
Agritech

Haryana agri-input company's field agents on ₹8,000 phones lose orders on patchy rural networks

What we'd do
Kotlin and Jetpack Compose offline-first app with a Room database, WorkManager sync and Hindi UI
What moves
Orders captured per agent up, sync failures down; tracked as sync failure rate before and after, over a fixed period
FMCG distribution

Delhi FMCG distributor's salesmen log retailer orders in WhatsApp without checking stock or credit

What we'd do
Android order-taking app with live stock, credit checks from Tally and UPI collection links
What moves
Order errors down, collection cycle days down
How a project runs

3 phases, each with a deliverable

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

Device and policy scoping

1 week

Analyse user devices, set minimum and target SDK, review Play policies, plan permissions

You get: Device matrix and policy checklist

We need: Analytics or a field device list, Play Console access

Build

6–12 weeks

Kotlin, Jetpack Compose, modular architecture, Baseline Profiles, unit and UI tests

You get: Internal-track build every sprint

We need: Product owner reviews, API access

Testing and launch

2–3 weeks

Device lab testing, closed test with the Play Console pre-launch report, Data safety form, staged rollout starting at 10% of users

You get: Live app at full rollout

We need: Store copy, privacy policy, testers

A typical engagement

From first call to result

Illustrative · not a client

Jaipur two-wheeler finance company, 300 field collection agents, Android-only fleet, collections tracked in Excel

Weeks 1–2Field studyRide along with agents, list devices and Android versions in use, map receipt and UPI flows; check first which OEM battery savers stop WorkManager jobsMinimum SDK, test device list and offline rules agreed
Weeks 3–9Design and buildKotlin, Jetpack Compose, Room offline queue, WorkManager sync, UPI intent collection, SMS receipts via DLT-registered templatesInternal-track build every week
Weeks 10–12Field pilot30 agents in one branch for three weeks; Android vitals, sync logs and battery use monitored; go if sync success stays above 99% (rule of thumb)Fix list and go/no-go decision
Weeks 13–15RolloutPrivate app via managed Google Play or staged public release, Hindi training videosAll 300 agents live
Where it startsagents on 3–4 GB RAM phones, handwritten receipts, two-day lag before collections reach the ledger
Where it endsAndroid app on every agent's phone with same-day ledger updates. Weekly watch: sync success rate, ANR rate, share of collections recorded the same day.
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
User-perceived crash rateDaily users with a user-perceived crash ÷ daily active usersBelow Google Play's 1.09% overall and 8% per-device bad-behaviour thresholdsPlay Console Android vitalsWeekly
User-perceived ANR rateDaily users with a user-perceived ANR ÷ daily active usersBelow Google Play's 0.47% overall and 8% per-device bad-behaviour thresholdsPlay Console Android vitalsWeekly
Download sizeCompressed download size from the Play Console app size reportSet a size budget from your baseline and block releases that exceed itPlay Console, Android Studio APK AnalyzerEvery release
Offline sync successQueued records synced within 24 hours ÷ records created offlineSet from the pilot baseline, then aim close to 100%App logs in Firebase or SentryWeekly
Automated by default

What runs itself after launch

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

When: Merge to mainPublish to internal or closed trackGitHub Actions with Gradle Play Publisher or Fastlane supplyRemoves: Manual uploads and version-code mistakes
When: Every upload to a testing trackReal-device crash checksGoogle Play pre-launch report and Firebase Test Lab robo testsRemoves: Crashes on devices the team doesn't own
When: DailyAndroid vitals alertsPlay Developer Reporting API pulled into Slack or Looker StudioRemoves: Missing a crash or ANR spike until ratings fall
Rules we work to

Standards and regulations

GoogleGoogle Play Developer Program Policies (Data safety, permissions, target API)

Declare data collection, justify sensitive permissions and meet the yearly target API deadline to keep shipping updates

Google (Android Developers)Android core app quality guidelines

Visual, functional, performance and security checklist used in release reviews

OWASPOWASP MASVS

Android Keystore storage, network security config and root or tamper checks for finance apps

What's changing

Platform and policy updates that affect this work

We track: Android Developers Blog, Play Console Help: policy announcements.

Google PlayNew apps and updates must target Android 16 (API level 36); existing apps need API 35 to reach new users

Android 16 removes the edge-to-edge opt-out for apps targeting it; layouts need retesting

Google PlayNew apps and updates targeting Android 15 or higher must support 16 KB memory page sizes

Native libraries and third-party SDKs must be rebuilt or updated to comply

Before you hire anyone

Questions to ask any agency, including us

Which Android versions would you drop, and how will you decide?

Why ask

Each version kept adds testing; dropping too many loses users

A good answer

A decision from your analytics or Play Console data, showing user share per version

Who will own the Data safety form and permission declarations?

Why ask

Wrong declarations lead to rejection or removal from Play

A good answer

A named owner, an SDK data audit, and a recheck every release

Will you set up our Play Console with individual roles rather than shared logins?

Why ask

Shared logins break audit trails and risk losing the account

A good answer

Organisation account in your name, agency users with limited permissions, 2-step verification for all

FAQ

Questions buyers ask us

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

Which Google Play policies must a new Android app meet in 2026?

New apps and updates must target a recent API level, support 16 KB memory pages, complete the Data safety form accurately, and offer account deletion both inside the app and through a web link.

  • From 31 August 2026, new apps and updates must target Android 16 (API level 36); Google raises this requirement every year.
  • Since 1 November 2025, apps targeting Android 15 or higher must support 16 KB page sizes, which affects native libraries and older NDK builds.
  • Broad photo and video permissions are restricted; most apps must use the system photo picker instead.
  • Data safety answers must cover every SDK, including analytics and crash reporting. A mismatch with what an SDK actually sends is a common reason for rejection.
How do you measure Android app stability after launch?

We track Play Console's Android vitals and Firebase Crashlytics, keeping the user-perceived crash rate under 1.09% and ANR rate under 0.47%, the thresholds above which Google Play may reduce an app's visibility.

  • Per-device thresholds are 8%, so one popular budget phone model with problems can drag the app down on that device.
  • Baseline Profiles and R8 shrinking cut cold-start time and APK size; we measure startup with Macrobenchmark before release.
  • Staged rollouts to 5–20% of users catch regressions before everyone receives the update.
Can our field team's app be kept off the public Play Store?

Yes. Apps for staff or distributors can be published privately through managed Google Play, so only devices enrolled by your organisation can install them, or distributed through a closed testing track while numbers are small. Private apps still benefit from Play's update system and Android vitals. We set this up under your organisation's Play Console and device management account, not ours.

  • Managed Google Play for private apps
  • Closed testing for small groups
  • Accounts held by your organisation
Should we build a native Android app or a cross-platform app?

Choose native Kotlin when Android is where almost all your users are, when the app relies heavily on background work, sensors or hardware, or when it must run well on very low-end phones. Choose a cross-platform framework when you need iOS at the same time and the app is mostly forms, lists and content. We weigh your users, features and team skills before recommending either.

  • Native for hardware and low-end phones
  • Cross-platform when iOS is needed too
  • Decide on users and features
Back to the service

Mobile app development →

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.