In this article
- Key takeaways
- Three Ways to Build an Android App in 2026
- Build Effort, Speed and Hiring
- Performance on Low-Cost Phones and App Size
- Device Features and Long-Term Upkeep
- Google Play Rules That Apply Whatever You Choose
- What Drives the Cost
- A Decision Table for Android Projects
- Picking the Stack That Fits Your Next Three Years
- Frequently Asked Questions
Before anyone quotes you for an Android app, one technical decision shapes most of the budget: will it be built natively in Kotlin, or with a cross-platform framework such as Flutter or React Native? That choice decides who you hire, how fast the first version ships, how the app behaves on a budget phone in Indore or Coimbatore, and how much work every yearly Google Play update needs.
This guide explains each approach as it stands in November 2026, what changes between them, the Play Store rules that apply whichever you pick, and how to decide. It focuses on trade-offs, not code.
Three Ways to Build an Android App in 2026
- Native Android (Kotlin and Jetpack Compose). Google's documentation says Android development is Kotlin-first and recommends starting new apps in Kotlin. For screens, Jetpack Compose is described as Android's recommended modern toolkit for building native UI. Google also supports Kotlin Multiplatform for sharing business logic between Android and iOS, while each app keeps its own native screens if you want.
- Flutter. The Flutter FAQ describes it as Google's open source framework for natively compiled apps for mobile, web, desktop and embedded devices from a single codebase. Apps are written in Dart, and Flutter draws its own interface rather than using Android's built-in widgets.
- React Native. Apps are written in JavaScript or TypeScript using React, and render through components that map to the platform's native UI building blocks. React Native 0.82 was the first version to run entirely on the New Architecture, 0.84 made Hermes V1 the default JavaScript engine, and the latest release when we checked was 0.88, published on 19 October 2026. In 2026 the project also moved to the React Foundation, an independent foundation. The official getting started guide recommends building new apps with a framework such as Expo.
All three are used in production. The question is which fits your product, your team and the next three years of upkeep.

Build Effort, Speed and Hiring
If you need Android only, native Kotlin is the most direct route: one codebase, Google's own tools and documentation, and no extra layer to keep in step with Android releases. If you need Android and iOS together, a cross-platform framework lets one team share most of the code, which usually means fewer people and one set of business logic to test. The saving is not total: platform-specific screens, permissions, store listings and testing still take separate effort.
Hiring follows the language:
- Kotlin developers are Android specialists. If you later add iOS, you need Swift skills or a Kotlin Multiplatform setup.
- Flutter needs Dart. The Flutter FAQ notes that experience with Java, Kotlin, Swift, TypeScript or C# helps developers learn Dart quickly, but Dart is rarely used outside Flutter, so check that your vendor or team has shipped Flutter apps before.
- React Native lets developers who already know React build native apps, which helps if your web product is built in React and the same team will own the app.
Whichever you pick, budget for at least one person who understands Android itself: Gradle builds, signing keys, permissions and Play Console.
Performance on Low-Cost Phones and App Size
Many Indian users run apps on entry-level phones with limited memory and storage. Each approach handles this differently:
- Native Kotlin runs directly on Android's runtime and can use Google's performance tools. Google states that Baseline Profiles improve code execution speed by about 30% from the first launch for the code paths they cover.
- Flutter uses its Impeller rendering engine. Flutter's Impeller page says it is enabled by default on Android API 29 and above, and that on older Android versions or devices without Vulkan support, Flutter falls back to its older OpenGL renderer. Test on the oldest, cheapest phones your customers actually use.
- React Native runs your JavaScript on the Hermes engine. Heavy logic, long lists and animations need care, and the New Architecture was built partly to remove earlier limits on layout and rendering.
On size, a native app carries only your code and libraries. The Flutter FAQ explains that a Flutter app's bundle includes the Flutter engine and framework code as well as your own code and assets, and React Native apps likewise ship their runtime. For a small app on a phone short of storage, that baseline matters. Do not judge size from a debug build: Flutter's app size guide points to the download and install figures in Play Console's Android vitals, which reflect what users actually download.
We found no official like-for-like benchmark of the three on Indian budget phones, so ask for a test build on your own target devices rather than trusting percentage claims.
Device Features and Long-Term Upkeep
Native Kotlin gets every new Android API on the day it ships. Flutter and React Native reach device features through plugins or native modules; when one does not exist or is poorly maintained, a developer writes the Android part in Kotlin anyway. Flutter's platform integration docs describe tools for this, such as platform channels and Pigeon. Before choosing, list the features you need, such as camera, Bluetooth, background location, UPI payment flows, KYC, maps and push notifications, and check that each vendor SDK you plan to use supports your framework.
Upkeep is where the choice keeps costing money:
- Native: you track Android and Jetpack library updates.
- Flutter: you track Android plus Flutter and Dart releases and every plugin you depend on.
- React Native: you track Android plus React Native releases, Expo SDK versions if you use Expo, and npm packages. Apps still on the old architecture face a real migration, since 0.81 was the last version that allowed the Legacy Architecture.
The React Native team has said recent releases (0.83, 0.86 and 0.88) had no user-facing breaking changes, which eases upgrades, but each extra layer is one more thing that must move before Google's yearly deadline.
Google Play Rules That Apply Whatever You Choose
These rules come from Google, not the framework, and they apply to every Android app on Play:
- Target API level. Google's target API page says that from 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher, with exceptions for Wear OS, Automotive, TV and XR apps. Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer Android versions. Extensions ran only to 1 November 2026. Expect this deadline to move up each year.
- 16 KB memory pages. Google's page size guide says apps targeting Android 15 and higher must support 16 KB page sizes on 64-bit devices, and from 1 February 2027 updates that do not support them cannot be released. This affects any app with native libraries, which includes Flutter and React Native apps (React Native added support in version 0.77), so keep frameworks and SDKs current.
- App bundles. Since August 2021, new apps must be published as Android App Bundles.
- Developer accounts. Play's sign-up page lists a one-time US$25 registration fee when we checked on 11 November 2026. Organisation accounts need a D-U-N-S number, and personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before production. For a business app, use an organisation account.
- Developer verification. Google's developer verification guide says protections start on 30 September 2026 for users in Brazil, Indonesia, Singapore and Thailand, expanding globally in 2027. Google's June 2026 update says over 99% of Play apps were registered automatically; check your Play Console home page for any that were not.
What Drives the Cost
These factors move an Android budget, roughly in order of impact:
- Platforms. Android only, or Android and iOS. This is the main reason to consider cross-platform at all.
- Screens and custom design. More screens and bespoke animation mean more build and test time in any framework.
- Device features and SDKs. Each payment, KYC, maps or hardware integration adds work, and more if the SDK lacks a ready plugin for your framework.
- Backend and integrations. APIs, admin panels, CRM or ERP links often cost as much as the app itself.
- Offline use and languages. Offline sync and Hindi or regional language support add design and testing effort.
- Device testing. The range of budget and mid-range phones you test on.
- Yearly upkeep. Target API updates, framework upgrades, library fixes and policy changes, every year.
Our guide to mobile app development cost in India covers these drivers in more depth, and the app development cost calculator helps you see how scope changes the estimate.
A Decision Table for Android Projects
| Your situation | Usually the better fit |
|---|---|
| Android only, heavy use of device hardware or background work | Native Kotlin and Jetpack Compose |
| Most users on budget phones, performance and size are critical | Native Kotlin, or test cross-platform builds on target phones first |
| Android and iOS from day one, custom branded design | Flutter |
| Existing React web team who will own the app | React Native (with Expo) |
| Android and iOS, but want native screens on each | Native apps with Kotlin Multiplatform for shared logic |
| Quick MVP to test demand on both platforms | Flutter or React Native, whichever your team knows |
If you are comparing vendors, our pages on Android app development and cross-platform app development set out what each kind of project involves.
Picking the Stack That Fits Your Next Three Years
Start from the platforms you truly need, the device features you depend on and the phones your customers carry. If the answer is Android only and close to the hardware, go native. If you need both platforms with one team, Flutter and React Native are both serious choices, and your team's existing skills should usually decide between them. Whatever you choose, plan for Google's yearly target API deadline and test on real budget phones before launch.
Frequently Asked Questions
Is Kotlin still Google's recommended language for Android?
Yes. Google's documentation says Android development is Kotlin-first and recommends starting new apps in Kotlin, with Jetpack Compose as the recommended modern toolkit for native UI.
Which is cheaper for an Android app, Flutter or React Native?
Neither is cheaper by default. Cost depends on platforms, screens, device features, integrations and testing. A team that already knows React may move faster with React Native; a team experienced in Dart may move faster with Flutter.
What target API level does Google Play require in 2026?
From 31 August 2026, new apps and updates must target Android 16 (API level 36). Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer Android versions.
Do Flutter and React Native apps work on cheap Android phones?
Yes, but test them. Flutter's Impeller engine is the default on Android API 29 and above and falls back to OpenGL on older devices or those without Vulkan. Both frameworks ship a runtime with the app, which adds to its size.
Does React Native still use the old bridge?
No. React Native 0.82 runs entirely on the New Architecture, and 0.81 was the last version that allowed the Legacy Architecture. Hermes V1 became the default JavaScript engine in 0.84.
Want help with this?
Talk to our team about software development.
Read next

Hiring Dedicated Developers in India (2026): Models, Costs and Pitfalls
Staff augmentation, dedicated team or managed delivery: which suits your managers, and what monthly rates leave out.
Read article
Custom-Built CRM vs Off-the-Shelf: Cost and How to Decide
When a custom CRM is worth building instead of configuring Salesforce, HubSpot or Zoho, what really drives the cost and how to decide.
Read article
Mobile App Development Cost in India: What Actually Drives the Price
Quotes differ because briefs are vague. Give every vendor one feature-level scope, budget for the backend and plan for the costs after launch.
Read article
Comments
Be the first to share your thoughts on this article.