Android App Development Company in India · 3 Nov 2026 · 7 min read · By Amit Kumar Sharma

Choosing an Android app development company in India: stack, testing and Play rules

Android apps break on budget phones and OEM skins in ways iOS apps rarely do. Here's how to pick the stack, test properly and clear the 2026 Play Console rules.

Key takeaways

Choose Kotlin for Android-only or hardware-heavy apps, Flutter for both platforms on one budget.
Insist on a device matrix covering OEMs, low-RAM phones and Android versions.
From August 31, 2026, new apps and updates must target Android 16 (API 36).
Publish from an organization account to avoid the 12-tester, 14-day closed test rule.

An Android app development company in India has one built-in advantage for Android work: the team lives in one of the most device-diverse Android markets in the world, where budget phones, heavy OEM customizations and patchy networks are everyday conditions. That experience matters if your app needs to run well on more than the latest Pixel and Galaxy flagships. This guide covers how to choose between Kotlin and Flutter, what proper fragmentation testing looks like, the Google Play Console rules that block launches in 2026, and what drives cost.

Kotlin vs Flutter: choosing the stack

Most new Android apps are built either natively in Kotlin (with Jetpack Compose for UI) or with Flutter, which also produces an iOS app from the same code.

Question	Pick Kotlin + Compose if…	Pick Flutter if…
Which platforms?	Android only, or Android first with a separate iOS team	Android and iOS together
Hardware and OS integration	Heavy use of background services, Bluetooth, NFC, foreground services, widgets	Standard features: camera, maps, payments, push, location
App size and low-end devices	Every megabyte matters for your users	A somewhat larger install size is acceptable
Design	You want standard Material behavior	You want one custom design on both platforms
Budget	Android is the only platform you're paying for	You need two platforms for close to the price of one

Kotlin Multiplatform is a third option some teams use to share business logic while keeping native UI. It works well for teams with strong native skills on both sides, but it's less common for early-stage products. For a broader comparison, see our guide to Flutter app development.

Device fragmentation: what real testing looks like

"We tested it on our phones" is not a test plan. Android apps break in ways iOS apps rarely do: aggressive battery managers on some OEM skins kill background work, low-RAM devices restart activities, and screen sizes range from small budget phones to foldables and tablets. Ask any team for a device matrix that covers:

Android versions: your minimum supported version through the latest release. Check your target market's version spread in Play Console once you have users.
Manufacturers: Samsung plus the OEMs that matter in your markets, such as Xiaomi, OPPO, vivo, realme, OnePlus and Motorola. Their battery and notification settings behave differently.
Price tiers: at least one low-RAM, entry-level device. If it runs well there, it runs well everywhere.
Form factors: small screens, large screens, foldables and tablets if you support them, plus font scaling and display size settings.
Network conditions: slow and intermittent connections, offline mode and switching between Wi-Fi and mobile data.

A practical setup mixes a small physical device lab for daily work with a cloud device farm, such as Firebase Test Lab, for broader automated runs before each release. After launch, Android vitals in Play Console show crash and ANR (app not responding) rates by device, and Google can reduce the visibility of apps that exceed its bad-behavior thresholds, so stability is also a distribution issue.

Play Console rules that block launches in 2026

Google Play's requirements change every year, and several of them can stop a launch outright. Verify these with your team before you plan a date:

Target API level

From August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher, and existing apps must target at least Android 15 (API 35) to stay available to new users on newer devices. Google offers an extension to November 1, 2026 through Play Console. Details are on Google's target API requirements page. Raising the target level is often real work, because new Android versions change behavior around permissions, background tasks and edge-to-edge display.

Closed testing for new personal accounts

If your app is published from a personal developer account created after November 13, 2023, you must run a closed test with at least 12 testers who stay opted in for 14 consecutive days before you can apply for production access, and that review usually takes up to seven days, per Google's testing requirements. Publishing from an organization account avoids this, which is one more reason to register as a company.

Developer verification

Google's Android developer verification program requires apps to be registered to a verified developer. Enforcement began on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, with global expansion planned from 2027, according to the Android Developers Blog. Most Play developers are already verified, but check your Play Console status.

Declarations and policy forms

Data safety form that matches what your app and its SDKs actually collect.
Health apps declaration, which every app must complete, even if only to state it has no health features.
Sensitive permissions such as SMS, call log, background location and all-files access need a justified core use case and a declaration.
Account deletion in the app and through a web link, if users can create accounts.
Financial services and loan app declarations for fintech apps. Our lending app development guide covers the extra rules.

Get a fixed quote for your app in 24 hours

Tell us what you're building. You get a written scope, timeline and fixed price — plus free Google Play and App Store submission and one month of launch marketing with every build.

Get my free quote WhatsApp us

Performance on real-world Android

Beyond passing review, an Android app has to feel fast on modest hardware. A good team works on:

App size: Android App Bundles, resource shrinking and on-demand delivery for large features.
Startup time: baseline profiles and lazy initialization of SDKs, which are a common cause of slow cold starts.
Background work: WorkManager for deferrable tasks, with testing on OEMs that restrict background activity.
Notifications: the runtime notification permission, channels, and handling devices where users or OEM settings block delivery.

What Android development in India costs

As with any app, scope drives cost: screens, user roles, backend, admin panel and integrations. Indian agencies typically charge well below US and UK agency rates for comparable Kotlin or Flutter work, with senior native developers costing more. Use ranges only for planning, and compare fixed-price quotes against the same written scope.

Android-specific cost factors to budget for:

A wider QA matrix than iOS, especially if your users are on budget devices.
Annual target API updates, which are a maintenance cost, not a one-off.
Policy work for sensitive permissions, financial or health apps.
The one-time Google Play developer registration fee (currently $25).

See the 2026 app development cost guide for ranges by app type, and our guide to app maintenance and support for what upkeep costs after launch.

A typical Android project, step by step

Timelines vary with scope, but a well-run Android build usually follows this order:

Scope and stack decision. Agree on Kotlin or Flutter, the minimum Android version, the device matrix and the analytics events you'll need for marketing.
Accounts first. Register your organization's Play Console account and start any verification early, since identity checks can take time.
Design and architecture. Flows, UI system, backend contracts and an offline strategy if your users have unreliable networks.
Sprints with internal test builds. Each sprint ends with a build you install from Play's internal testing track, so you test on your own phone.
Closed or open testing. A wider beta on real devices, plus policy forms completed in parallel: data safety, permissions, content rating and the health declaration.
Production release. A staged rollout to a small percentage of users first, watching crash and ANR rates before going to 100%.

Staged rollouts are one of Android's most useful safety nets. If a bad build slips through, you can halt it before most users get it.

Questions to ask an Android app development company in India

Kotlin or Flutter for my app, and what would change your recommendation?
What's in your device test matrix, and which devices are physical?
What target API level and minimum Android version will you ship with?
Who handles the data safety form, permission declarations and policy emails from Google?
Will the app be published from my organization account?
How do you handle Android vitals issues after launch?

Working with Appryze on Android

Appryze builds Android apps in Kotlin or Flutter from Delhi for clients in the USA, UK, UAE and India. Every build comes with a fixed-price written quote within 24 hours, free Google Play submission, one month of launch marketing and weekly written updates, and you own the code and the Play Console account. Learn more on the Studio page, or compare with our iOS development guide.

Frequently asked questions

How much does it cost to build an Android app in India?

It depends on scope: number of screens, user roles, backend, admin panel and integrations. Indian agencies typically charge well below US and UK agency rates for comparable work. Get fixed-price quotes against the same written scope, and budget separately for QA across devices and yearly target API updates.

Should I use Kotlin or Flutter for my Android app?

Use Kotlin with Jetpack Compose if you only need Android or rely heavily on background services, Bluetooth, NFC or other hardware features. Use Flutter if you need Android and iOS from one codebase with a consistent design. Both are mature, well supported and capable of passing Google Play review.

What is the Google Play target API level requirement for 2026?

From August 31, 2026, new apps and app updates must target Android 16, which is API level 36, or higher. Existing apps must target at least Android 15 to remain available to new users on newer Android versions. Developers who need more time could request an extension to November 1, 2026 in Play Console.

Do I need 12 testers to publish on Google Play?

Only if you publish from a personal developer account created after November 13, 2023. Those accounts must run a closed test with at least 12 testers opted in for 14 consecutive days before applying for production. Organization accounts are not subject to this rule, so registering as a company avoids the delay.

How do Android developers test across different devices?

Good teams combine a small lab of physical devices, covering major manufacturers, a low-RAM budget phone and different screen sizes, with a cloud device farm such as Firebase Test Lab for wider automated runs. After launch, Android vitals in Play Console show crash and ANR rates by device model.