Blog · APPS

Android App Development for Businesses: What to Get Right

In India, most of your customers carry an Android phone, so app development for Android is usually where a business app starts. Android also has its own rules: Play Console verification, a closed-testing requirement for new accounts, yearly target API deadlines and thousands of device models. Here is what to get right.

By Nitish, Biz HoistPublished 2 November 20267 min read
Last updated November 2026
Smartphone with app interface modules, toggles and settings around it

Why Android usually comes first in India

The short answer: Android app development for a business means building the app (in Kotlin, or cross-platform with React Native or Flutter), testing it on a range of real devices, and publishing it through a Google Play Console account. As of November 2026, new apps and updates must target Android 16 (API level 36), and new personal developer accounts must run a 14-day closed test with at least 12 testers before going live.

The large majority of smartphones sold in India run Android, across a very wide price range. For a business whose customers are spread across cities and income levels, an Android app reaches the most people for the first launch.

That reach comes with a catch: your app will run on cheap phones with little memory, on flagship phones, on tablets, and on everything in between. Most of the work in Android development is making sure it behaves well on all of them.

Native (Kotlin)

Android only. Full access to every Android feature and the best performance, but iPhone needs a separate app later.

Android-only products

Cross-platform

React Native or Flutter. One codebase for Android and iOS, with native screens. Most business apps fit here.

Most business apps

WebView wrapper

Your website inside an app shell. Fast to make, but limited and a poor fit for anything customer-facing.

Internal tools at most

We compare the last two in detail in React Native vs WebView wrapper apps.

Setting up Google Play Console

Before anything goes live you need a Google Play Console developer account. Create it in your business's name, not your developer's, so you own the listing, reviews and downloads.

  1. Choose the account type

    Google offers personal and organisation accounts. A registered business should normally use an organisation account; the requirements differ by type.

  2. Pay the registration fee

    As of November 2026 it is a US$25 one-time fee, per Google's official registration page. Check that page for the current amount.

  3. Verify your identity

    Google may ask for a government ID and a card in your legal name. If the details are judged invalid, the fee is not refunded, so enter them carefully.

  4. Verify an Android device

    Personal account owners must confirm access to a real Android device through the Play Console mobile app before publishing.

  5. Run the required testing

    New personal accounts must complete a closed test before they can publish to everyone (details below).

The 12 testers, 14 days rule

Google's testing requirements page says personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in continuously for at least 14 days. Only then can you apply for production access.

From first build to public launch on a new personal account

Internal testyour own team
Closed test12+ testers
14 daysopted in throughout
Applyfor production
Public launchafter review

Plan at least two to three weeks between "the app is ready" and "the app is live" for a new account.

Pick testers who will actually use the app: staff, loyal customers, family members with different phones. Their feedback on cheap and old devices is worth more than the count itself.

Target API levels and yearly deadlines

Every Android app declares a "target API level": the Android version it was built and tested for. Google raises the minimum every year so apps keep up with security and privacy changes.

SituationRequirement as of November 2026
New apps and app updates (phones and tablets)Must target Android 16 (API level 36) or higher, from 31 August 2026
Existing apps that are not updatedMust target Android 15 (API level 35) or higher to stay available to new users on newer Android versions
ExtensionGoogle allowed extensions to 1 November 2026, which has now passed

Source: Android Developers' target API level requirements. Wear OS, Android TV, Automotive and XR apps have different levels.

This is why an Android app is never "finished". If nobody updates it for a year or two, you cannot ship even a small bug fix until the target level is raised, and that can mean code and library changes.

Device fragmentation: what actually breaks

Fragmentation is the word for Android running on thousands of devices from many manufacturers, on different Android versions and with different custom skins. These are the issues that cause most real-world bug reports:

Screen sizes

Small budget phones, tall screens, notches, tablets and foldables. Layouts must flex, not assume one size.

Battery savers

Some manufacturers' skins aggressively stop background apps, which can delay notifications or sync.

Low memory

Entry-level phones with little RAM close heavy apps. Image sizes and memory use matter.

Patchy networks

Apps must handle slow or dropped connections gracefully, with retries and saved state.

Older Android versions

Your minimum supported version decides which phones can install the app at all.

Permissions

Newer Android versions ask for notification, location and photo access differently. Ask only when needed.

The practical answer is testing on a spread of real phones, not just the emulator on a developer's laptop. A budget phone, a mid-range phone from a different brand and one recent flagship catch most problems.

Apps outside the Play Store

Some businesses distribute Android apps directly as an APK, for example field-staff tools. Google is adding Android developer verification for this: Google scheduled protections to begin on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, and Google says it will roll out globally in 2027. If you plan to share an app outside Play, budget time to register as a verified developer.

Is an Android-only app right for you?

Android-only can make sense if…
  • Your customers or staff are almost all on Android
  • It is a field or warehouse tool on company phones
  • You want to test demand before spending on iOS
Build for both if…
  • Your customers include many iPhone users
  • The app is part of your brand, not just a tool
  • You want one codebase to maintain, not two later

If you are earlier in the journey, our guide on how to make an app covers the whole process from idea to launch, and app development cost in India explains what drives the budget.

Frequently asked questions

How to app development for Android: where do I start?

People often search "how to app development for android" when they mean "how do I get an Android app built". Start by writing down the three or four things the app must do, decide native or cross-platform, then plan a Play Console account in your business name and time for closed testing.

How much does a Google Play developer account cost?

As of November 2026, Google charges a one-time registration fee of US$25. Check Google's official Play Console help page for the current amount before you sign up.

What is the 12 testers rule on Google Play?

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in for at least 14 days before they can apply to publish to everyone.

What is a target API level?

It is the Android version an app is built and tested for. Google raises the required level every year. From 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher.

Should I build in Kotlin or a cross-platform framework?

Kotlin suits Android-only apps that need deep device features or top performance. If you will want an iPhone app too, a cross-platform framework such as React Native or Flutter lets one codebase serve both.

Why does my app work on one phone but crash on another?

Usually because of device differences: screen size, Android version, memory, battery-saving settings or permissions. Testing on several real phones from different brands catches most of these issues before launch.

Planning an Android app?

Tell us what your app needs to do and which devices your customers use, and we will plan the build, testing and Play Store launch with you, with a fixed quote within one business day. See how we work on our app development page.

Get a fixed quoteApp development
Chat on WhatsApp