How to Make an Android App: Design to Google Play
How to make an Android app step by step: scope, Material 3 design specs, Kotlin and Compose or cross-platform, closed testing rules and Google Play.

This guide is for founders, indie developers and PMs who want to ship an Android app without learning every lesson the hard way. It covers the full path from idea to a live Google Play listing: scoping, designing to Material 3, choosing a build approach, the testing rules for new developer accounts and what Google reviews before you go live.
TL;DR: Scope one core job, design with Material 3 specs (48 dp touch targets, edge-to-edge layouts, adaptive window sizes), and build with Kotlin and Jetpack Compose or a cross-platform framework if you also need iOS. Register a Google Play developer account, run the required testing track, upload an Android App Bundle, complete the Data safety form and store listing, then submit for review.
What you need before you start
| Requirement | Notes |
|---|---|
| A computer | Android Studio runs on Windows, macOS, Linux and ChromeOS, so no special hardware is needed |
| Android Studio | Google's free IDE with emulators, layout tools and build system |
| A Google Play developer account | One-time 25 USD registration fee, plus identity verification |
| At least one real Android phone | Emulators are good, but test performance, camera and notifications on hardware |
| A privacy policy URL | Required for apps that handle personal or sensitive data, and requested in Play Console |
You can install your own builds on any phone you own without an account, so testing starts on day one.
Step 1: Scope the smallest useful app
Write a single sentence describing who the app is for and the one outcome it delivers. Then list only the screens needed to deliver that outcome end to end. For a bill-splitting app that might be: onboarding, create group, add expense, balances, settle up. Everything else waits.
If you have not validated the idea, do it now; our guide to MVP app design shows how to cut scope without cutting the value.
Step 2: Design to Material 3
Android users have strong expectations shaped by Google's own apps and Material Design. Following them saves design and engineering time because Jetpack Compose's Material 3 components implement these specs out of the box.
Key Android design specs
| Element | Material 3 spec |
|---|---|
| Minimum touch target | 48 × 48 dp |
| Body text | Body Large 16 sp; Body Medium 14 sp |
| Top app bar (small) | 64 dp tall |
| Navigation bar (bottom) | 80 dp tall, 3 to 5 destinations |
| Floating action button | 56 dp standard |
| Standard side margin | 16 dp on phones |
| Corner radius scale | 4, 8, 12, 16 and 28 dp steps from extra small to extra large |
Units matter: dp (density-independent pixels) for layout and sp (scale-independent pixels) for text, so type respects the user's font size setting. Common design bases are 360 × 800 dp and 412 × 915 dp.
Android behaviors to design for
- •Edge-to-edge. Apps targeting Android 15 and later draw behind the status and navigation bars by default. Design backgrounds full bleed and keep content within window insets.
- •System back. Every screen must handle the back gesture predictably. Predictive back shows a preview of where back leads, so do not intercept it without reason.
- •Dynamic color. On Android 12 and later, Material You can derive app colors from the user's wallpaper. Decide whether to support it or keep fixed brand colors.
- •Screen sizes. Android runs on small phones, foldables and tablets. Material's window size classes help: compact (under 600 dp wide), medium (600–840 dp) and expanded (840 dp and up). Swap the bottom navigation bar for a navigation rail on wider windows.
- •Notifications permission. Since Android 13, apps must request permission to post notifications. Ask in context, after explaining the benefit.
For a deeper look at applying Material 3 to real screens, read Material Design 3 Expressive on real Android screens. If you do not have a designer, you can generate a first draft of Material-style Android screens in floow and refine them through chat before writing any code.
Step 3: Choose how to build it
| Approach | Best for | Trade-offs |
|---|---|---|
| Kotlin + Jetpack Compose | Android-first apps, deep platform features, best performance | Android only |
| Flutter | One codebase for Android and iOS, highly custom UI | Larger app size; Material widgets are reimplemented, not native views |
| React Native (often with Expo) | Teams with React skills shipping both platforms | Native modules sometimes need extra work |
| Kotlin Multiplatform | Sharing business logic across platforms while keeping native UI | More setup; UI sharing via Compose Multiplatform is newer |
| No-code builders | Simple apps, prototypes, internal tools | Platform limits and lock-in |
Google recommends Kotlin and Jetpack Compose for new native Android apps, and Android Studio's "Empty Activity" template starts you with a Compose project. If you also need an iPhone version, compare this with our guide to making an iPhone app; a cross-platform framework often costs less when both platforms launch together. Our broader post on how to build a mobile app goes deeper into the trade-offs.
A minimal Compose screen
@Composable
fun BalancesScreen(balances: List<Balance>) {
Scaffold(
topBar = { TopAppBar(title = { Text("Balances") }) }
) { padding ->
LazyColumn(contentPadding = padding) {
items(balances) { b ->
ListItem(
headlineContent = { Text(b.name) },
trailingContent = { Text(b.amount) }
)
}
}
}
}
Scaffold, TopAppBar and ListItem give you Material 3 spacing, typography and theming with almost no custom code.
Step 4: Build, then test on real devices
Android device variety is real. Before you invite testers:
- •Test on at least one small, older phone and one recent flagship.
- •Rotate the screen and resize the window (split screen, foldables if you can).
- •Turn the font size and display size to maximum.
- •Switch between light and dark themes, and gesture versus three-button navigation.
- •Deny every permission, then grant it later from system settings.
- •Kill the app in the background and reopen it to check state restoration.
Step 5: Set up Google Play Console
- •Create a developer account and choose personal or organization. Organization accounts need a D-U-N-S number and business verification.
- •Pay the one-time registration fee and complete identity verification.
- •Create the app in Play Console with its default language, name and whether it is free or paid. Free apps cannot later be changed to paid.
- •Pick a permanent application ID, for example
com.yourcompany.splitbills. It cannot change after publishing. - •Enroll in Play App Signing. Google manages your app signing key; you sign uploads with a separate upload key, which can be reset if lost.
Step 6: Use the testing tracks
Play Console offers internal, closed and open testing tracks before production.
| Track | Who | Use it for |
|---|---|---|
| Internal testing | Up to 100 testers you add by email | Fast builds for your team, available within minutes |
| Closed testing | Testers you invite by email list or Google Group | Wider beta with real users |
| Open testing | Anyone who finds the opt-in link or listing | Public beta at scale |
| Production | Everyone in your chosen countries | Release, optionally staged by percentage |
Important for new personal accounts: Google requires newer personal developer accounts to run a closed test with at least 12 testers who stay opted in for 14 consecutive days before applying for production access. Plan for this in your launch timeline and recruit testers early; check Play Console for the current requirement on your account.
Step 7: Prepare the store listing and policy forms
Google Play requires:
- •App name (up to 30 characters), short description (up to 80) and full description (up to 4,000).
- •App icon at 512 × 512 px PNG. Make your adaptive launcher icon with the app icon generator.
- •Feature graphic at 1024 × 500 px.
- •Screenshots: at least 2 and up to 8 per device type.
- •Data safety form: what data you and your SDKs collect, share and why.
- •Content rating questionnaire, target audience and ads declaration.
- •App access instructions if parts of the app need login, so reviewers can get in.
Step 8: Upload and submit for review
- •Build a signed Android App Bundle (.aab), which Google Play requires for new apps. Play generates optimized APKs per device from it.
- •Make sure your app targets a recent Android API level; Google enforces a minimum target API for new apps and updates each year.
- •Create a release on your chosen track, add release notes and roll it out.
- •Review times vary; new accounts and apps can take several days. Google emails you if changes are needed.
Pre-submission checklist
- • App launches and core flows work on small and large screens
- • Touch targets at least 48 × 48 dp; text in sp
- • Edge-to-edge layout with correct insets
- • Back gesture behaves predictably on every screen
- • Permissions requested in context with clear reasons
- • Data safety form matches actual data collection, including SDKs
- • Privacy policy URL live and accurate
- • Reviewer login credentials provided if needed
- • Closed testing requirement met (new personal accounts)
- • Store listing assets uploaded at correct sizes
Step 9: Launch with a staged rollout
Use a staged rollout for production, releasing to a small percentage of users first and increasing it as crash rates stay healthy. Watch Android vitals in Play Console for crashes, ANRs (app not responding) and excessive battery use. Reply to reviews, fix the top issues and ship small updates often.
FAQ
How much does it cost to publish an Android app?
Google Play charges a one-time 25 USD developer registration fee. Google also takes a service fee on paid apps and in-app purchases; check Google's current rates, since subscriptions and smaller developers have reduced tiers.
Can I make an Android app for free?
You can build and test an Android app for free with Android Studio and your own phone. Publishing on Google Play requires the one-time registration fee. Our guide to creating an app for free covers the free tools available.
Should I use Kotlin or Java for Android?
Kotlin. Google has recommended Kotlin as the preferred language for Android development for years, and Jetpack Compose, the modern UI toolkit, is Kotlin-only. Java is still supported for existing codebases.
How long does Google Play review take?
It varies. Many updates are reviewed within hours to a few days, while new apps and new developer accounts can take longer. Factor in the 14-day closed testing period if your personal account is subject to it.
Do I need a separate design for Android and iOS?
Your brand, content and flows can be shared, but navigation, controls and platform behaviors should follow Material 3 on Android and Apple's guidelines on iOS. Users notice when an app ignores their platform's conventions.
Design it with floow
Get your Android screens right before you open Android Studio. Describe your app in floow and export the result to Jetpack Compose, Flutter, React Native or Figma. Try:
Design a 5-screen Android bill-splitting app following Material 3: onboarding, groups list with a floating action button, add expense form, balances screen with who owes whom, and a settle-up confirmation. Use a bottom navigation bar, 48dp touch targets and a calm green color scheme.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights18 November 2026Mobile App Usability Testing: A Lightweight MethodA practical mobile app usability testing method for small teams: recruit 5 users, write tasks, run sessions on real phones, and turn findings into fixes in a.By floow.design
Guides18 November 2026iOS Human Interface Guidelines: A Practical SummaryThe iOS Human Interface Guidelines summarized: layout, safe areas, type sizes, color, navigation, controls, gestures and accessibility, with specs and a.By floow.design
Roundups18 November 20268 Uizard Alternatives for AI App Design (2026)Compare 8 Uizard alternatives for AI app design: who each tool suits, mobile screen quality, Figma and code export, and how to pick the right one for your.By floow.design