Here is how to make an Android app for a business, in one sentence: agree on the single job the app must do, design its screens, choose native Kotlin or one cross-platform codebase, build the app with the server behind it, test it on real phones and publish it through a Google Play Console account. The code is rarely what surprises people. Google's rules are: identity checks, a 14-day closed test for new personal accounts, a minimum Android version every update must target, and a privacy form even for apps that collect nothing.
I have spent 18 years in software development; my team at 26 Lines of Code builds Android apps in Kotlin and Flutter, backend included, as part of our mobile app development work. Below is the path we walk with clients, and a checklist to forward to your team.
In October 2026 I measured the five guides Google showed me for these searches. One, from 2022, gets a beginner from the idea to the Play Store in ten evenings, which Google's 14-day closed test now rules out for new personal accounts. None mentions that test, the target API level or the Data safety form, and two still call Java the main language. Five pages are a small sample; still, they mark where the surprises hide.
How to make an Android app in eight steps
Every business app passes eight steps, and the last column shows where the calendar slips. Most guides on how to build an Android app stop at the code, yet steps six and seven set the launch date.
| Step | What gets decided | Where the time goes |
|---|---|---|
| 1. The one job | Who uses the app, and for what | Agreeing what waits for version two |
| 2. Design | Every screen, for every role | Rounds of comments |
| 3. Native or cross-platform | Android alone, or Android plus iPhone | Little, once the job is clear |
| 4. Build | App, API, database, admin panel | Integrations |
| 5. Testing | Phones and Android versions | Phones nobody on the team owns |
| 6. Play Console | The account, its type and owner | Identity checks, D-U-N-S, the closed test |
| 7. Listing and review | The store page | Review: up to seven days for some accounts |
| 8. Launch and updates | Rollouts, crash rate | Each new Android version |
Step six need not wait for step five. Open the account when the project starts, and its checks run while the app is built.
Start with the one job, then design for it
Before anyone explains how to create an app for Android, decide what it is for: who will use it, and the one task it must do better than your website, a phone call or a paper form. Everything else waits for the second version.
That answer also tells you whether you need an app at all. An app is worth building when people come back often, when it relies on what only a phone has (camera, location, notifications, offline work) or when the app is the product. If customers find you once and call, a mobile-friendly website is enough; if they want a home-screen icon without a store in between, a progressive web app can be added straight from the browser.
Design comes next, because a screen is cheaper to change than code: every screen, for every role, on phones from compact to foldable. In Tarot Fans, one app serves both clients and tarot experts, each role with its own home screen, so every screen had to work for both. That is why we settle each role's screens with the client in discovery, before the build.
Native Kotlin or one codebase for Android and iPhone
This is the main technical fork in Android app development, and your users decide it. Native means an app for Android only; today that means Kotlin with Jetpack Compose, written in Android Studio. Cross-platform means one codebase in Flutter (Dart) or React Native (JavaScript), built into an Android app and an iPhone app.
Google recommends starting new Android apps in Kotlin. It calls Jetpack Compose "Android's recommended modern toolkit for building native UI", and Android Studio is its official development environment. Java is still supported, but I would not start a new app in it.
| Native Android | One cross-platform codebase | |
|---|---|---|
| An iPhone app later | A second project | Built from the same code |
| New Android features | As soon as Google ships them | Once the framework or a plugin supports them |
| Best fit | Android-heavy audiences, apps that lean on the camera, sensors or Bluetooth | Ordering, booking, marketplaces, internal tools |
| Our example | SaneBox | Tarot Fans, Mutualz |
SaneBox is the native case: an AI email assistant; we designed its Android app and built it with Kotlin and Jetpack Compose, and it is live on Google Play. Mutualz, a German restaurant app, runs on one Flutter codebase in both stores, in German and English. Our guides to cross-platform app development and Android vs iOS development go deeper.
What sits behind the app
Almost every business app needs a backend: an API, a database for accounts and orders, and an admin panel for your staff. Check that it is in every quote you compare; an app with accounts and no server is half a project.
Two of our apps show what that means. In SaneBox, the code that talks to the server is generated from the service's OpenAPI description, so the app does not fall behind when the service changes. Tarot Fans has a Django backend, with Agora under its live sessions and calls and a Stripe wallet where clients pay and experts withdraw.
Payments follow a Google rule worth settling before the design. Digital goods sold in the app, such as subscriptions or premium features, go through Google Play's billing (or an approved alternative where Google allows one) and carry a service fee whose US rates changed on June 30, 2026. Physical goods and services, such as food delivery, rides or event tickets, are paid through your own provider.
Test on real phones, not only the emulator
What counts is how the app runs on the phones your customers own, not on the developer's. The Android Studio emulator simulates phones, tablets and other devices on a computer, across Android versions, network speeds and locations, and catches a lot early. Real phones in real hands find the rest: how the app feels on the model your customers actually bought. Ask for the list of test phones and Android versions before the build, and check it against your customers' phones.
Play Console adds two tools. Within minutes of an upload, up to 100 internal testers can install the new build, so your staff try it on their own phones. Each uploaded build also gets a pre-launch report: Google installs it on a set of Android devices in its test lab and reports stability, performance and accessibility issues. On our projects, a tester also goes through each release before it ships.
Your Google Play Console account: fee, identity and the 14-day test
Every app on Google Play goes out from a Google Play developer account, which deserves more thought than it gets. Registration is a one-time $25. Google verifies the developer's identity and may ask for a government ID and a card in the same legal name; new personal accounts must also prove access to a real Android device through the Play Console app.
| Personal account | Organization account | |
|---|---|---|
| Google asks for | Legal name, address, contact email and phone | A D-U-N-S number; the organization's name, address, phone and website |
| Lead time | Identity checks | Identity checks, plus the D-U-N-S number: free, up to 30 days |
| Before production | If created after November 13, 2023: a closed test, 12 or more testers opted in without a break for 14 days or more | No such test |
My advice to every client: an organization account registered to your company, with the company as the owner. The owner is the first account registered; it invites the developers and sets what each can touch, app by app. Google can move an app between accounts, but only the account holding it can start the transfer, so an app in a developer's personal account stays there until that developer cooperates.
The rules every release must pass
Four technical rules apply to every app and update on Google Play:
- The target API level. From August 31, 2026, Google Play accepts a new app or an update only if it is built for Android 16, which is API level 36. An app left on Android 14 or older stops being offered to people who have not installed it yet, once their phones run a newer Android.
- The Android App Bundle. Required for new apps since August 2021; Google Play turns it into a download with only what each device needs.
- App signing. The key that signs what users install stays with Google; your team signs uploads with a separate upload key, which Google can reset if it is lost.
- The Data safety form. It is required of every app, including one that collects no data, and must also declare what the app's SDKs gather for analytics, crash reports or ads. It needs a privacy policy and shows on the listing before anyone installs.
The listing, the review and the launch
The listing is the app's sales page, within Google's limits: a name of up to 30 characters, a short description of up to 80 and a full one of up to 4,000, a 512 by 512 icon, a 1024 by 500 feature graphic and at least two screenshots, or four of at least 1080 pixels to qualify for Google Play's recommended formats. Write for people: Google warns that repetitive or irrelevant keywords can get an app suspended.
Then comes the review. For certain accounts Google says it can take up to seven days, or longer in exceptional cases; a 2020 guide in my sample still promises a few hours. Announce the launch date after the approval.
The first release cannot be staged, but each update can: a staged rollout goes to a percentage of users first, and you can halt it. Google also watches stability: if the share of daily users who hit a crash passes 1.09%, or who see the app freeze (an ANR) passes 0.47%, Google Play may reduce the app's visibility and warn people on its listing.
What an Android app costs, and what drives the price
With us, the first version of an app starts at $5,000: the smallest app that does its one job, written with AI tools, with an engineer's code review and testing before release. On our projects a person works in a pair with AI, so the routine code goes fast and the hours go into decisions. No client's code goes into training AI; our agents carry the best practices we arrived at over years of projects. Your estimate costs nothing and comes before any contract.
| What raises it | Why |
|---|---|
| Two native apps | Every screen and rule exists twice, in two languages |
| User roles | Every role adds screens and permission rules |
| Integrations | Code in the app and on the server |
| Live chat, calls or video | A server that answers in real time |
Budget for upkeep too, because an app ages without new features; that is mobile app maintenance, and under an app support contract we react to a breakdown the same day, weekends included. Need more Android hands for your own team? Our developers can join it through staff augmentation, from $35 an hour; the pricing page lists every starting price we have.
The Android launch checklist
Knowing how to develop an Android app is your team's job; knowing what to check is yours. Forward this list, and tick it off before a launch date goes into any calendar:
- The app's one job fits in one sentence, and version one holds nothing else.
- The Google Play developer account is an organization account owned by your company, and developers work in it with the permissions you gave them.
- The D-U-N-S number was requested when the project started; on a personal account, 12 testers are lined up for the 14-day closed test.
- It is built for Android 16 (API 36) and ships as an App Bundle.
- You know who holds the upload key.
- The Data safety form covers every SDK, and the privacy policy link opens.
- Builds went to your customers' kinds of phones through the internal track; the pre-launch report is clean.
- The listing has its texts, a 512-pixel icon, a 1024 by 500 feature graphic and four screenshots of at least 1080 pixels.
- The launch date leaves up to seven days for review.
- Updates go out as staged rollouts, someone owns the crash rate, and the upkeep after launch has a budget.
Before you commit: the limits and the mistakes
When an Android app is not the right first step
- Your customers mostly carry iPhones. StatCounter, which counts page views on more than a million sites, put Android at 46% of US mobile traffic and 69% worldwide in September 2026; your own analytics beat both numbers.
- You need a form for a dozen employees. Then learning how to make an app without coding may beat hiring a team, if a no-code builder's subscription and limits suit you.
- Nobody will fund updates. An app left alone stops reaching new users on newer phones, while a progressive web app updates like a website.
Mistakes few avoid
Most advice on how to make an Android app is about code; these mistakes are not:
- The app lives in the developer's account, and only that account can start a transfer.
- The account is opened in the last week, when a D-U-N-S number can take up to 30 days and a new personal account still needs its 14-day test.
- The Data safety form forgets the SDKs that collect data for analytics, crash reports or ads.
If you would rather walk this path with a team that has done it, that is our Android app development work. Tell us who the app is for and what it should do; on weekdays from 9 am to 6 pm Miami time we reply within 30 minutes, and the rough estimate is free.
Questions
Where do I start if I want to create an app?
Write one sentence: the people the app is for, and the one task it must do better than your website or a phone call. Add the roles, what it connects to and the date that matters, and a team can estimate it.
How long does it take to make an Android app?
The build depends on the scope; with us its timeline is in the contract, and every two weeks you see working software in a demo. Add Google's calendar: up to 30 days for a D-U-N-S number, a 14-day closed test for a new personal account and up to seven days of review for some accounts.
How much does it cost to put an app on Google Play?
Google charges $25 once, when you register the developer account. If the app sells digital goods through Google Play's billing, Google also takes a service fee on those sales.
Can I make an Android app without coding?
Yes, with a no-code builder, for a staff tool or a pilot with a few users. For a product customers rely on, code you own is worth more than a builder's subscription and limits.
Should I launch on Android or iPhone first?
Ask your analytics: they show which phones your customers carry. If they split between both, one cross-platform codebase often costs less than two separate apps.