Questions, answered plainly

An AI app builder for Android apps that runs in your browser. You describe the app you want in plain English or pick a template; the AI asks a few questions, builds the screens with a live preview, and gives you a signed APK and an AAB for Google Play. It is a no code app builder where the "no code" part is a conversation rather than a canvas.

Open the builder and sign in with Google. It works on a computer or a phone browser; nothing to install.

No. If you can describe the app to a friend, you can describe it to the builder.

Building and previewing are free. The AI runs on your own OpenAI API key, so you pay OpenAI directly at their price, with 0% commission from us. Builder Pro ($7/month) unlocks the APK and AAB. See pricing.

It is the password-like key that lets apps use your OpenAI account. Create one at platform.openai.com/api-keys, add billing or credit to your OpenAI account, and paste the key into the builder when it asks. It is saved only in your browser. Our step-by-step guide walks through it.

Android 7.0 (API 24) and newer.

No. The APK and AAB are built and signed in the cloud. A phone browser is enough to build and download your app.

Anything made of screens, lists, forms and data: business, shops, menus and ordering, booking, trackers, quizzes, catalogues, community and event apps, portfolios, internal tools. With native features: camera, location, notifications, biometrics, barcode scanning. See the use cases.

3D games, heavy video or audio processing, and large platforms such as marketplaces with payouts or social networks.

Not today. It makes Android apps: an APK to install and an AAB for Google Play.

Yes. Connect your own Supabase project from the builder and the AI wires sign-in and shared data into your screens. Simple apps can keep their data on the phone instead.

Yes. Connect Stripe or PayPal in the builder's Payments panel; shop and booking apps can then take real payments. Prices come from your own data, never from the phone.

It can load data from any public CSV or JSON URL, including one on your website. It does not wrap or convert a website — for that, a website-to-app converter is the right tool.

A first working version in a few minutes; a polished app in an evening or two. The APK and AAB build in about three minutes each. Publishing adds Play's review time.

Say it in the chat: name the screen and the change. Or turn on edit mode, tap + on a card or section, and describe the change. The iteration guide has a playbook.

Yes. The design pickers for the bottom bar, top bar and side menu apply instantly and need no AI.

Describe what you did, what you expected and what happened; it fixes the specific screen. You can also say "undo" to roll back the last change.

No. Describe the layout in words and the colours; the builder produces clean, consistent screens in your palette.

Two files from Get your app: an APK you can install on any Android phone (scan the QR code) and an AAB, the format Google Play requires. Both are signed with your account's key.

No. The builder delivers finished, signed apps rather than a project to compile. That is what keeps it no-code from start to finish.

Yes. No licence fee, no badge, no revenue share. Publish it under your own name and sell it if you like.

Yes, under your own developer account. Upload the AAB; the publishing guide covers the account, the listing and the data-safety form.

Your app's identity on Google Play: every update must be signed with the same key. One is created for your account on the first build. Download a backup from Advanced settings and keep it safe, or upload a key you already use.

Play reviews behaviour and policy compliance, not how the code was written. Apps ask only for the permissions their features use, which keeps the data-safety form short and honest. You still need a privacy policy URL.

Yes. Send the APK; phones show an 'unknown sources' prompt. Common for internal, school and event apps.

In your browser, on the device you build on. Clearing this browser's site data removes them, so build on one browser you keep.

Your request and the relevant project files go from your browser straight to OpenAI, on your own API key, so the AI can build what you asked. They do not pass through our servers.

No ads. Sign-in uses Google's Firebase Authentication to keep your Builder Pro plan with your account. See the privacy policy.

Only what you built it to. A local-only tracker collects nothing; an app connected to your Supabase project stores data there, under your control.