What this guide covers: going from an app idea to a published Google Play app without learning Java or Kotlin.
Android runs on most of the world's smartphones. Publishing an app there used to mean learning Java or Kotlin, wrestling with Android Studio and reading thousands of pages of documentation. Today you can describe your app in plain English and let Claude Code do the programming, while you make the decisions: what the app does, how it looks and who it's for.
By the end of this guide you'll know how to:
- choose the right kind of app and the simplest technology for a beginner
- set up Claude Code and the tools Android apps need
- build a real app and test it on your own Android phone
- prepare it for Google Play: icon, screenshots, privacy policy and store listing
- get through Google Play's testing requirements and publish
Fees, testing rules, policies and technical targets change regularly. Confirm them on Google's official Play Console help pages before you rely on them.
- You make the decisions; Claude Code does the programming
- No Java, Kotlin or Android Studio expertise needed to start
- Google Play rules change, so always check the current ones
Compare the Expo and native Kotlin routes, see why Expo suits beginners, and list everything you need.
- ✓One codebase for Android, iPhone later
- ✓Test instantly on your phone with Expo Go
- ✓No heavy setup; easy cloud builds
- ✓Very advanced features may need extra work
- ✓Google's own tools and language
- ✓Full access to every Android feature
- ✓Google's recommended route
- ✓Bigger setup, slower for beginners
There are two popular routes. Claude Code is good at both, but one is much easier for beginners.
| Route | What it means | Pros | Cons |
|---|---|---|---|
| Expo (React Native) | One codebase that runs on Android (and iPhone later) | Test instantly on your phone with the Expo Go app; no heavy setup; easy cloud builds | Very advanced phone features may need extra work |
| Native (Kotlin + Android Studio) | Google's own tools and language | Full access to every Android feature; Google's recommended route | Bigger setup, heavier tools, slower for beginners |
Recommendation for your first app: Expo. You can test on your real phone within minutes, and the same app can become an iPhone app later. If you prefer to go native, Claude Code can guide you through Android Studio in the same way. The planning, testing and publishing chapters of this guide apply to both.
What you need
- A computer (Mac, Windows or Linux)
- An Android phone for testing (an emulator works too, but a real phone is easier for beginners)
- Claude Code on a paid Claude plan
- Node.js, a free tool Expo needs. Claude Code can tell you how to install it.
- A free Expo account (for cloud builds)
- A Google Play Developer account when you're ready to publish (a one-time registration fee applies; check the current amount)
An emulator works, but testing on a real Android phone is easier for beginners.
- Expo is the easiest route for a first Android app
- Planning, testing and publishing chapters apply to both routes
- A real Android phone is easier for testing than an emulator
Choose a small, focused, genuinely useful first app, avoid risky ideas, and capture it in a clear app brief.
Google Play is full of apps. The ones that do well as a first project are small, focused and genuinely useful. Google also rejects apps that are low-quality copies, so your app must do something real.
Good first-app ideas
| App | Who it's for | Why it works |
|---|---|---|
| Water intake tracker with reminders | Health-conscious people | Simple, daily use, clear value |
| Tip and bill splitter | Friends eating out | One screen, instantly useful |
| Kids' times-table quiz | Parents and teachers | Fun, focused, repeat use |
| Plant care reminders | Houseplant owners | Reminders + a list |
| Shift-pay calculator | Hourly workers | Saves real time each week |
| Prayer or meditation timer | Spiritual or wellness users | Simple, calm, daily habit |
| Gym rep counter and log | Gym beginners | Simple data, personal records |
| Unit converter for a niche | Bakers, builders, nurses | Specialised beats generic |
| Habit streak tracker | Anyone building routines | Motivating daily use |
| Local event checklist | Wedding or party planners | Lists + countdown |
Avoid for your first app
- Anything needing logins, payments or a server
- Apps that copy a famous brand or game
- Apps handling sensitive data such as health records or money transfers
- "Wrapper" apps that just show an existing website (Google Play often rejects these)
Write your app brief
APP BRIEF Name: SipStreak One sentence: A water tracker that reminds me to drink and shows my daily progress. Main screen: a big glass that fills up as I log drinks; +250ml and +500ml buttons; today's total. Other screens: History (last 30 days as a bar chart); Settings (daily goal, reminder times). Must have: log drinks, daily goal, reminders, history saved on the phone. Out of scope: accounts, cloud sync, ads, payments. Look and feel: fresh, calm, soft blues, rounded shapes, big friendly buttons.
List what the app won't do, such as accounts, cloud sync, ads and payments, so your first version stays small.
- Google rejects low-quality copies, so your app must do something real
- Avoid logins, payments, servers, sensitive data and website wrappers
- A brief sets screens, must-haves, out-of-scope items and look
Let Claude Code install what's missing, create your Expo project and show the app live on your phone.
Open Claude Code in a new empty folder called sipstreak and let it guide the setup. Paste this:
I'm a complete beginner and I want to build an Android app with Expo (React Native). I'm on [Mac/Windows]. Please check what's installed on my computer (Node.js, npm) and guide me through anything missing, ONE step at a time. Wait for me to say "done" before the next step. Then create a new Expo project in this folder and explain the main files in plain English.
Claude will check for Node.js, help you install anything missing and create the project. It will also tell you to install Expo Go from Google Play on your phone.
See your app on your phone
Ask Claude to start the development server. You'll see a QR code in the terminal or app. Open Expo Go on your phone, scan the code, and the starter app appears on your phone. Your computer and phone usually need to be on the same Wi-Fi network.
From now on, every change Claude makes shows up on your phone within seconds.
From now on, every change Claude makes shows up on your phone within seconds.
If the phone can't connect, tell Claude exactly what you see. Common fixes include the "tunnel" connection option or checking both devices share a network.
- Ask Claude to guide setup one step at a time
- Scan the QR code with Expo Go to see your app
- Phone and computer usually need the same Wi-Fi network
Build your app in six safe steps: plan, main screen, extra screens, polish, real-user testing and checkpoints.
Step 1: Plan first
Switch Claude Code to plan mode (Shift+Tab in the terminal, or the mode menu in the desktop app) and paste your brief:
Here is my app brief: [paste brief] Propose a plan: the screens, how the user moves between them, how data is saved on the phone, how reminders will work, and the order you'll build things. Flag anything that's tricky on Android, such as notification permissions. Keep it simple and explain in plain English.
Read the plan. Ask about anything you don't understand. Approve it.
Step 2: Build the main screen first
Build only the main screen first: the glass that fills up, the +250ml and +500ml buttons and today's total. Save the data on the phone so it survives closing the app. Tell me when it's ready to test.
Test it on your phone. Tap the buttons. Close the app completely and reopen it. Is the total still there?
Test it on your phone. Tap the buttons. Close the app completely and reopen it. Is the total still there?
Step 3: Add screens one at a time
Now add the History screen with a bar chart of the last 30 days, and a tab bar at the bottom to switch between Today and History.
Now add the Settings screen: daily goal and reminder times. Ask the user for notification permission in a friendly way, and explain on screen why reminders need it.
Step 4: Make it feel polished
Make the app feel premium: a smooth animation when the glass fills, a little celebration when I hit my goal, consistent spacing, large touch targets, and support for dark mode. Check the text is readable for people with low vision.
Step 5: Test like a real user
Make a list and give it to Claude in one message:
- What happens on a small phone? A big tablet?
- What happens at midnight? Does "today" reset correctly?
- What if I deny notification permission?
- What if I set a goal of zero, or 50,000?
- Does it work in airplane mode?
I tested the app and found these issues: [your list]. Fix them one at a time, and explain each fix in one sentence.
Step 6: Save checkpoints
Ask Claude to set up Git and save a checkpoint after each working feature. If a later change breaks something, you can return to the last good version.
Ask Claude to set up Git and save a checkpoint after each working feature, so you can return to the last good version.
- Ask for a plan and flag tricky Android areas first
- Build one screen at a time and test each on your phone
- Give Claude your whole test list in one message
Gather everything Google Play needs besides the app: graphics, honest listing text, privacy policy and console forms.
Before you publish, you need several things besides the app itself.
Your Google Play checklist
| Item | What it is | How Claude helps |
|---|---|---|
| App name | Up to the character limit Google allows | Suggests names and checks they're clear |
| App icon | High-resolution square icon | Creates icon ideas; you can refine with an AI image tool |
| Feature graphic | A banner shown on your store page | Designs the layout and text |
| Screenshots | Phone screenshots of key screens | Suggests which screens and captions to show |
| Short and full description | Your store text | Writes clear, honest descriptions |
| Privacy policy | A web page explaining what data you collect | Drafts it from what your app really does; you check it |
| Data safety form | Questions in the Play Console about data use | Explains each question in plain English |
| Content rating | A questionnaire about your app's content | Explains the questions |
| Package name | A unique ID such as com.yourname.sipstreak | Sets it in the app config |
Write an honest store listing
Write a Google Play listing for my app: a short description and a full description. Be honest: only describe features the app really has. Use short paragraphs and a bullet list of features. No hype, no claims about health results.
Create a privacy policy
Even a simple app needs a privacy policy if it's on Google Play. Ask:
Be honest: only describe features the app really has.
Look at my app's code and list exactly what data it collects, where it's stored and whether anything leaves the phone. Then draft a plain-English privacy policy based on that. Mark anything I should confirm.
Host the policy on a free web page (Claude Code can make a simple one, and Chapter 6 of Claude Code From Zero shows how to publish a page). Paste the link into the Play Console.
Ask Claude to list exactly what data your app collects, where it's stored and whether anything leaves the phone, then draft the policy.
- Claude can draft names, graphics layouts, listings and form explanations
- Even a simple app needs a privacy policy on Google Play
- Base the privacy policy on what your code really does
Create the Android App Bundle Google Play requires, using Expo's EAS Build, and handle your signing key safely.
Google Play needs an Android App Bundle (an .aab file), not the development version you've been testing. With Expo, the easiest way to create one is EAS Build, Expo's cloud build service.
Help me create a production Android App Bundle for Google Play using EAS Build. Walk me through it one step at a time, including signing keys. Explain what each step does, and wait for me after each one.
Claude will guide you to:
Letting Expo and Google Play manage your signing key is the beginner-friendly option. If you manage it yourself, back it up somewhere safe.
- Google Play needs an .aab file, not your development version
- EAS Build is the easiest way to create one with Expo
- Losing a self-managed signing key can make updates very difficult
Open your developer account, set up the app in Play Console, pass closed testing and apply for production.
Step 1: Create your developer account
Sign up for a Google Play Developer account in the Play Console. You'll pay the one-time registration fee and verify your identity. Choose a personal or organisation account. Organisation accounts may need extra details such as a D-U-N-S number.
Step 2: Create the app in Play Console
Add your app, fill in the store listing, upload the icon, graphics and screenshots, and complete the content rating, data safety and target audience sections.
Step 3: Testing tracks
Google Play has testing tracks: internal, closed and open testing. New personal developer accounts must run a closed test with a minimum number of testers for a minimum period before they can publish to everyone. At the time of writing this was 12 testers for 14 continuous days, but check the current requirement in the Play Console.
To find testers:
Ask testers to use the app for real and send you feedback.
- friends and family with Android phones
- a local community group or club related to your app's topic
- online communities where developers test each other's apps (be genuine: actually use their apps and give feedback)
Ask testers to use the app for real and send you feedback. Fix issues, upload new versions to the testing track, and keep notes. Google may ask what you learned from testing.
Step 4: Apply for production access and publish
When the testing requirement is met, apply for production access, answer the questions honestly, and submit. Reviews can take from hours to several days. If something is rejected, Google tells you why. Paste the message into Claude and ask:
Google Play rejected my app with this message: [paste]. Explain what it means in plain English and what I need to change. Then make the code changes and update the listing text if needed.
In online communities where developers test each other's apps, actually use their apps and give feedback.
- New personal accounts must run a closed test before publishing
- Fix issues, upload new versions and keep notes on what you learned
- If rejected, paste Google's message into Claude for a fix
Find your first users, keep improving through updates, and understand the ways apps can earn later on.
Get your first users
- Share with friends, family and communities who'd find it useful
- Ask happy users to leave a review
- Write a short post or video showing the problem your app solves
Improve with updates
Read every review. Fix bugs fast. Add one feature at a time. Each update needs a higher version number. Ask Claude:
Prepare a new release: increase the version number, list the changes for the "What's new" text, and build a new App Bundle.
Ways apps can earn (later)
When you have users, you can explore:
Read every review. Fix bugs fast. Add one feature at a time.
- a one-time "Pro" upgrade that unlocks extra features
- a subscription for ongoing value
- tasteful advertising
- building custom apps for local businesses or clients
Each of these brings extra rules: Google Play's payment policies, ad network policies, privacy requirements and tax. Learn them before adding any.
Write a short post or video showing the problem your app solves, and share it with communities who'd find it useful.
- Share with people who'd find it useful and ask for reviews
- Each update needs a higher version number
- Learn the payment, ad, privacy and tax rules before earning
Four reusable prompts and a 14-day plan that takes you from app idea to publishing.
3 2 1
Listing assets, Closed testing, then
Set up tools; see Build screens one developer account apply for Choose the app the starter app on at a time, then and first App production and and write the brief your phone polish and test Bundle publish
Prompts to keep
ONE STEP AT A TIME Walk me through this one step at a time. Wait for me to say "done" before the next step.
EXPLAIN THE ERROR Here's the error and what I was doing when it appeared: [paste]. Explain it in plain English, find the cause, then fix it.
POLISH PASS Review every screen for spacing, readability, touch target size, dark mode and small-screen layout. List issues, then fix them.
STORE-READY CHECK Check the app is ready for Google Play: version number, package name, icon, permissions requested (remove any we don't need), crash risks and privacy policy accuracy.
Your 14-day plan
| Days | Goal |
|---|---|
| 1 | Choose the app and write the brief |
| 2 | Set up tools; see the starter app on your phone |
| 3–5 | Build screens one at a time |
| 6 | Polish and test thoroughly |
| 7 | Icon, screenshots, listing, privacy policy |
| 8 | Developer account and first App Bundle |
| 9 onwards | Closed testing with real testers, improving as you go |
| After testing | Apply for production and publish |
Before publishing, ask Claude to check version number, package name, icon, permissions requested, crash risks and privacy policy accuracy.
- Keep prompts for step-by-step help, errors, polish and store checks
- Ship the small version and learn from real users
- Make version two better based on feedback
Follow Sam, a nurse with no coding experience, building ShiftPay from brief to closed testing.
Let's follow Sam, a nurse with no coding experience, who builds ShiftPay, an app that calculates take-home pay for shift workers with night and weekend rates.
Day 1: the brief
APP BRIEF Name: ShiftPay One sentence: Log my shifts and see what I'll earn this pay period, including night and weekend rates. Main screen: this pay period's shifts, total hours, estimated gross pay. Other screens: Add shift (date, start, end, break); Rates (base hourly rate, night %, weekend %, overtime rules); History. Must have: correct maths across midnight; saved on the phone; currency formatting. Out of scope: tax calculations (they vary too much), accounts, cloud sync, ads.
Sam deliberately leaves out tax. It's complicated and risky, and the app is useful without it. "Estimated gross pay" is honest.
Day 2: setup and first screen
Claude Code checks Node.js, creates the Expo project and starts the dev server. Sam scans the QR code with Expo Go and sees the starter app on their phone. Then:
Build the main screen and the Add Shift screen only. Save shifts on the phone. Show the total hours for the current pay period (I'm paid every 2 weeks starting on a Monday I'll set in Settings later; use this Monday for now).
Day 3: the hard part (time maths)
Shifts that cross midnight are where bugs hide. Sam asks Claude to protect them with tests:
Write automated tests for the hours and pay calculations before changing anything else: a day shift, a night shift crossing midnight, a shift crossing from Saturday into Sunday, a shift with an unpaid break, a shift on the night the clocks change, and overtime after 40 hours in a week. Then make the tests pass and explain any assumptions.
Claude flags an assumption: does the weekend rate apply by the hour or by the shift's start day? Sam checks their contract (by the hour) and tells Claude. This is exactly why you read Claude's assumptions: only you know the real rules.
Day 4: rates and settings
Add the Rates screen: base rate, night rate % (with night hours start/end), weekend rate %, overtime threshold and rate. Use these in the calculations. Show a breakdown on the main screen: base, night, weekend, overtime.
Day 5: polish
Polish pass: friendly empty states ("No shifts yet, tap + to add one"), large touch targets for tired hands at 3am, dark mode by default with a light option, and a clear disclaimer under the total: "Estimate before tax and deductions."Day 6: store preparation
Claude drafts the listing ("Track your shifts and estimate your pay, including nights and weekends"), a privacy policy (data stays on the device; nothing is collected), and suggests five screenshots. Sam designs an icon with an AI image tool and refines it in Canva.
Sam didn't need to learn Kotlin or React. Sam needed to know their own problem precisely, test honestly and make decisions when Claude asked.
Day 7: release build and Play Console
Sam creates a Google Play developer account, then:
Help me create a production App Bundle with EAS Build, one step at a time, and explain the signing key options.
The app is created in Play Console, the listing, data safety and content rating forms are completed, and the first build is uploaded to closed testing.
Days 8–10 and beyond: testers
Sam invites colleagues from work and a few friends with Android phones to the closed test. Two testers find issues: a confusing break field and a crash when the rate is left blank. Sam pastes the feedback into Claude Code, gets fixes, bumps the version and uploads a new build. After the testing period ends, Sam applies for production access.
Lesson: Sam didn't need to learn Kotlin or React. Sam needed to know their own problem precisely, test honestly and make decisions when Claude asked.
For tricky logic like shifts crossing midnight, ask Claude to write automated tests first, then make them pass and explain assumptions.
- Leaving out risky features like tax keeps the app honest
- Protect tricky calculations with automated tests first
- Read Claude's assumptions: only you know the real rules
Quick answers to common problems, from Expo Go connections and release crashes to rejections, testers and iPhone.
"Expo Go can't connect to my computer."
Make sure the phone and computer are on the same Wi-Fi network, or ask Claude to start the server in "tunnel" mode. Some office or public networks block device-to-device connections.
"The app works in Expo Go but the release build crashes."
Release builds are stricter. Ask Claude: "The release build crashes on launch. Help me get the crash logs from the device and find the cause." Common causes are missing environment settings, libraries that need native configuration, or code that only worked in development mode.
"Google Play rejected my app for policy reasons."
Paste the exact message into Claude and ask for an explanation and a fix list. Typical issues: missing privacy policy, inaccurate data safety answers, permissions that aren't justified, or misleading listing text.
"I can't find 12 testers."
Ask friends, family, colleagues and local groups related to your app's topic. Developer communities exist where people test each other's apps; be genuine and actually test theirs too. Check the Play Console for the current number of testers and days required.
Learning the basics helps you direct Claude better, so ask it to explain parts of your code as you go.
"Do I need to know Kotlin eventually?"
Not to publish useful apps. Learning the basics helps you direct Claude better, so ask it to explain parts of your code as you go. You'll pick up a surprising amount.
"Can I publish the same app on iPhone?"
With Expo, mostly yes. The same code can build for iOS, but you'll need an Apple Developer Programme membership, and building and testing is easiest with a Mac. See Build iPhone Apps with Claude Code and Xcode.
"How do I update the app after launch?"
Make changes, test, increase the version number, build a new App Bundle and upload it to a testing track or production. Add clear "What's new" notes.
Every update after launch needs a higher version number and clear "What's new" notes.
- Some office or public networks block device-to-device connections
- Typical rejections: missing policy, wrong data answers, unjustified permissions
- With Expo, the same code can mostly build for iPhone
Start small, ship your first version, then improve it with what real users tell you.