Now on Google Play — every new account starts with 100 free credits
How it works

From a sentence to an app on your phone in nine steps

Most people finish steps 1–5 in their first ten minutes. Steps 6–9 are the evening that turns a working draft into an app you would publish.

Describe

One paragraph in plain English: what the app is for, its tabs, what the first screen shows, the rules, where data lives, any native features, the look. The prompting guide has a formula and twelve examples.

Answer the interview

The builder asks the few questions that change the design. "You choose" is a valid answer; it will pick a sensible default and tell you.

Watch it generate

First the manifest, then one screen at a time. About a minute for a four-tab app. A short summary at the end says what it built and what it assumed.

Tap through the preview

The app opens inside a native Android shell on your phone: real tabs, real back button, real permission prompts. Use it like a customer would.

Refine by talking

One specific change per message — name the screen, say the change, describe the behaviour. Each request edits one file and costs a few credits.

Add native features

Camera, location, reminders, fingerprint, barcodes. Each becomes a declared capability with its permission and code.

Name, icon, colours

Set the app name, generate or upload an icon, confirm the theme. These live in the manifest and flow into the export.

Export

One tap produces a complete Android Studio project you own: Kotlin shell, your screens, only the libraries you use.

Build & publish

Open in Android Studio, sign, build a bundle, upload to Play. The publishing guide walks through every screen of the Play Console.

Under the hood

Why it edits instead of regenerating

The builder writes a manifest first and one file per screen. When you ask for a change it opens only the file that owns that screen, so nothing else moves, credits are spent only on the change, and a request never breaks a screen you already approved. The native shell reads the manifest to build tabs and navigation, which is why generated apps navigate like real apps and never fake a tab bar in HTML.

project.json → tabs, screens, colours, capabilities  ·  screens/*.html + *.js → one per screen  ·  shared/bridge.js → navigation and native calls  ·  Kotlin shell → app bar, tabs, permissions, adapters
Try it

Describe an app

Type one sentence. It opens the Android app where the real conversation happens.

Enter to build · opens the Android app

Build your first app tonight

Describe it in a sentence, watch the screens appear, tap through them on your phone. Free to start — 100 credits, no card, no code.

Get AI App Builder — free Android 7.0+ · Google Play