Questions, answered plainly

An Android app that builds Android apps. You describe the app you want in plain English; an AI agent interviews you, generates the screens and navigation, previews them natively on your phone and exports a complete Android Studio project. It is a no code app builder where the "no code" part is a conversation rather than a canvas.

No. If you can describe the app to a friend, you can describe it to the builder. If you do code, you get a clean project you can extend.

Every new account gets 100 free credits, enough for a small app. There is no subscription; further credits are bought as packs. Previewing, hand-editing and exporting cost nothing. See pricing.

Android 7.0 (API 24) and newer. Apps you build support the same range.

Not to build, preview or export. You need Android Studio on a computer (any OS) to compile the export into a Play-ready bundle — or someone who has it.

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

3D games, heavy video or audio processing, and apps that are mostly a backend (marketplaces with payments and payouts, social networks). It can make the phone-side screens for those; the server is separate work.

Not today. The builder runs on Android and exports Android projects. The screens are standard HTML/JS and portable, but the shell and export target are Android.

Yes, with a backend you connect — Firebase is the usual choice. The builder generates the screens and the calls; you set up the project. Most small apps do fine without accounts, loading content from a Google Sheet instead.

Not out of the box. Generated stores and booking apps send orders by WhatsApp, email or a form, or open a payment link. Native card payments need a provider's SDK added to the exported project.

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 under ten minutes; a polished app in an evening or two. Publishing adds Play's review time.

Say it in the chat: name the screen and the change. Each request edits one file. The iteration guide has a playbook.

Yes. Screens are plain HTML/JS you can open in the builder's editor or after export. Hand edits cost no credits and the AI reads them on the next request.

Describe what you did, what you expected and what happened; it fixes the specific screen. You can also undo a generation and rephrase.

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

A zip with a complete Android Studio project: Gradle wrapper, Kotlin shell (activity, navigation, bridge, one adapter per capability used), your screens and data in assets, a manifest with only the permissions your features need, and your launcher icon at every density.

Yes, outright. No licence, no badge, no revenue share. Modify it, sell it, hand it to a developer.

Yes, under your own developer account. The publishing guide covers the account, signing, the bundle, the listing and the data-safety form.

Play reviews behaviour and policy compliance, not how the code was written. Capability-driven exports declare minimal permissions, which makes the data-safety form short and honest. You still need a privacy policy URL.

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

On your phone, in the app's private storage. Nothing is published unless you export and share it.

The prompt and the relevant project files are sent to our server so the AI model can answer. They are not used to train models and are not shared with third parties beyond the model provider processing the request.

No ad SDK. Sign-in uses Google's Firebase Authentication to keep your credits with your account. See the privacy policy.

Only what you built it to. A local-only tracker collects nothing. The exported manifest and your own screens are the truth — read them before filling in Play's data-safety form.