To make an app without coding, describe it to an AI app builder, answer a few quick questions, let it build the screens, tap through the live preview, refine by chatting, then download the APK and AAB and publish. The first working version takes under ten minutes; a polished one takes an evening. This guide is that evening, step by step.
Step 0 — Decide what the first screen shows
Before you type anything, answer one question: when someone opens the app, what do they see? A menu. Today's habits. A list of bookings. A gallery. Everything else follows from that. People who skip this step get a generic dashboard and spend an hour steering away from it.
Step 1 — Write the idea in one paragraph
Not a spec. A paragraph, the way you would describe it to a friend:
Notice what is there: the name, the screens implied by verbs, the rules (hours, days), the one native feature (reminders) and the look. Our prompting guide has more, but that paragraph is enough.
Step 2 — Answer a few questions
Open the builder, sign in with Google and send your paragraph. It asks a few quick questions — the app's name, its main colour, bottom tabs or a side menu — with suggestions you can tap. Or choose "let the AI decide" and it picks sensible defaults and tells you what it picked.
Step 3 — Watch it generate
The screens appear one at a time in the live preview. Nothing to do here except read the short summary at the end, which tells you what it built and what it assumed.
Step 4 — Tap through the preview
The app runs in a phone frame beside the chat. Use it like a customer would: tap every tab, go into a detail screen, press the back button, try the form. Note what is wrong or missing — do not fix yet, just note.
Step 5 — Refine by talking
Now give feedback, one or two things at a time:
- "The slot grid should show a 30-minute lunch gap at 13:00."
- "Add a photo to each service."
- "Make the confirm button bigger and gold."
Each request edits only the relevant screen. You can also switch on edit mode and tap + on the card or section you mean. Small, specific requests use few AI tokens and never break other screens; "redo the whole thing but nicer" uses a lot and rarely helps.
Step 6 — Add native features
If you did not ask for them up front, this is when to add camera, location, notifications, biometrics or barcode scanning. Each one becomes a declared capability with its permission and code. See native features in no-code apps for what each does and when to ask.
Step 7 — Name, icon, colours
Confirm the app name (short — it truncates under the icon at about 12 characters) and the theme colour, and pick a design for the bottom bar, top bar or side menu (free, no AI needed). Upload your icon in Get your app.
Step 8 — Get your app
Tap Get your app and choose Try it on your phone. In about three minutes the APK is built in the cloud and signed with your account's key. The build is free.
Step 9 — Test the installed app
Scan the QR code with your phone's camera, download the APK and install it. It should behave exactly like the preview. Try it on a second phone if you can.
Step 10 — Publish
Choose Publish on Google Play to build the AAB, create a Google Play developer account, fill in the listing and upload the AAB. First-time review takes a few days. The publishing guide covers the listing, the data-safety form and the common rejections.
What usually goes wrong, and the fix
| Symptom | Cause | Fix |
|---|---|---|
| Generic dashboard, not my app | Prompt described features, not the first screen | Say what the home screen shows, in one sentence |
| Too many screens | Listed every future feature | Build the three screens that matter; add later |
| Change broke another screen | Asked for a vague "redesign" | Ask for one specific change at a time |
| Data disappears | Did not say what must be saved | "Save bookings on the phone" / "load menu from this sheet" |