Last updated 24 October 2026 · how the dashboard works, step by step: HTML to APK, text to APK, App Store screenshots, pricing and limits.
Black UI is a dashboard where you chat with AI and turn what it builds into a real Android app. It is designed for small apps written in HTML, CSS and JavaScript. There are two ways to get an installable APK (to install on a phone) and AAB (the bundle format Google Play asks for):
Either way the build ends the same: a signed APK and AAB produced on your own GitHub account, with a keystore password that never leaves your device. You do not need Android Studio or the Android SDK. Around that sit a few related tools: App Store screenshots, pointing at a button on a screenshot, and voice-overs, music and file tools.
Demo: from a prompt for a calculator app to an APK installed on a phone.
The first time you open Black UI you'll see a sign-in screen.
Choose your Google account. Google shares only your name, email address and profile picture with us — nothing else from your account.
Your account gets a unique ID, so your chats and usage limits are yours alone. To leave, use the sign-out button in the sidebar. To delete your account data, see the Privacy Policy.
Once you're signed in, every message goes to Gemini by default — no setup or key needed.
If auto-switch is on and you've added a Claude key, messages that look like real coding or debugging work (error text, "fix this bug", code blocks) are automatically routed to Claude instead.
Turn auto-switch off in Settings to pin every conversation to one provider.
Chatting with Gemini needs no key. For the extra features, open Settings and add:
Keys are stored locally on your device only and are sent directly to Anthropic or GitHub — never to our servers. If you clear your browser or app data, you'll need to add them again.

Attach a code file, screenshot of an error, or paste a stack trace directly into the chat. Once Claude is active, it reads the attachment, explains the bug, and can hand back a corrected file with a download link right in the conversation.
Tell the AI what you want: what the app does, the screens, colours and any rules. A calculator, a quiz, a habit tracker, a small game are all typical examples.
The AI writes the app as an HTML file and runs it in a preview frame inside the conversation. Tap the preview to open it full screen and use it like a real app.
Say what to change in plain words (“make the buttons bigger”, “add a dark theme”) and the preview updates.
When you like it, say “build this as an APK”. The AI adds a Start APK Build button to the chat. Continue with the build steps.

If you already have an HTML app, you do not need the AI to write it again.
Attach the file in the chat. It can come from another AI tool or from your own work.
Tell the AI to build the file as an APK. It shows the same Start APK Build button, and from there the steps are identical to Text to APK.
This is the same flow for both routes. A build costs 2 tickets (see pricing).
The button appears in the chat, along with the app’s package name.
Pick the image that becomes the app icon.
Enter a key and a password, then enter the password a second time to confirm. A .keystore backup file is saved to your device. Keep it safe: you need the same file and password for every future update of this app. Details are in your keystore password.
A GitHub token is required, because the build runs in your own GitHub account using your own Actions minutes. Black UI does not provide a key for this. See how to get your GitHub token.
Both files appear in the chat, together with the package name and key alias. Install the APK on a phone to test it, and keep the AAB if you plan to publish to Google Play.


When you ask the dashboard to build an Android app, it doesn't compile anything on our servers. It pushes your generated project to your own GitHub repository and triggers a build through your own GitHub Actions minutes, using a base Android scaffold we maintain and publish openly here:
github.com/thoibatrader-ship-it/apk-template — the exact base template every APK/AAB build starts from.
The template handles Gradle configuration, keystore signing and the GitHub Actions workflow that turns your code into an installable app. It is a shared, versioned starting point — not something regenerated from scratch per user — so:
Full terms for this feature are in Terms of Service — APK/AAB Builder.
When you build an APK/AAB, you set a password that signs the app. That password is encrypted on your own device before it ever leaves your browser:
Because we never see this password, we also can't recover it for you. Save your .keystore file and password somewhere safe — you'll need the same pair for every future update to the same app.
Store listings need clean, well-framed screenshots. After an APK build, Black UI can make them for you in two ways.
The button appears under a finished build. The AI reads your HTML app and decides which screens are worth capturing.
Your HTML file is sent to your own GitHub account, where the screens the AI chose are opened and captured. The raw screenshots come back to the dashboard. This step costs 1 ticket and gives up to 20 screenshots per run.
Each raw screenshot is placed on a canvas with a matching background colour, a short tag and a subtitle, so it looks like a store screenshot instead of a bare capture. This step happens in your browser and costs no tickets.
Open your app yourself, take screenshots, attach them to the chat and ask the AI to make them ready for a store listing. The designing happens in your browser, so this route costs no tickets.
You can download the raw and the designed versions together as one zip. Store size and count requirements differ between stores and change over time, so check the current rules of the store you publish to.


Describing where to click (“bottom right, under the third icon”) fails on crowded pages such as government portals or large dashboards. Black UI does it visually instead.
This is best-effort, so double-check before submitting forms or making payments. The screenshot is sent to an AI model, so hide OTPs, passwords and ID numbers before you attach it.

Black UI uses two things, and they pay for different work:
Every new account gets a one-time grant of free coins and tickets (the amounts are shown in the app). You can top up any time in the Shop. A purchase that includes coins moves your account to a paid plan with access to additional models; ticket-only packs do not.
| Pack | Coins | Tickets | Price (INR) |
|---|---|---|---|
| Starter Combo | 1,000 | 2 | ₹39 |
| Pro Builder Combo | 3,500 | 6 | ₹129 |
| Ultimate Agency Pack | 12,000 | 20 | ₹399 |
| Coins: Starter | 1,000 | – | ₹29 |
| Coins: Pro Builder | 3,500 | – | ₹99 |
| Coins: Ultimate | 12,000 | – | ₹299 |
| 2 Tickets | – | 2 | ₹19 |
| 6 Tickets | – | 6 | ₹49 |
| 20 Tickets | – | 20 | ₹149 |
Prices match the in-app Shop at the time of writing. The Shop always shows the current price. Your own Claude API usage is billed to you by Anthropic, and GitHub Actions minutes are between you and GitHub; neither is included in these packs.
Every APK/AAB build runs on your own GitHub account, using your own GitHub Actions minutes. GitHub enforces its own usage limits on those minutes (for example, the free tier's monthly Actions minutes) — limits we don't set and can't override from our side.
If you've already purchased Black UI build tickets but your GitHub account hits GitHub's own limit, the build can't proceed until GitHub resets it (typically at the start of your next billing cycle) or you upgrade your GitHub plan. A Black UI ticket pays for our dashboard's build orchestration — it doesn't purchase or extend GitHub's infrastructure, which stays entirely between you and GitHub.
Black UI currently runs on Google's free Gemini API quota for free-plan users and on Razorpay (INR) for payments, so the service is offered in India only at the moment. We plan to support more countries and currencies as the product grows — thanks for bearing with us.
Every purchase comes with a GST invoice. To make that possible, the Shop asks for one thing before you pay: your billing state.
On the Android app, if your phone can't save the PDF, tap View to see the full invoice on screen. The website always lets you download the PDF. See the Privacy Policy for exactly what we store.
Attach the HTML file in the Black UI chat and ask for an APK. Tap Start APK Build, choose a logo, set a keystore key and password, and the signed APK and AAB are built on your own GitHub account. It takes 2 tickets. See the build steps.
Yes. Describe the app, try the live preview in the chat, then ask for an APK. See Text to APK.
No. The build runs on GitHub Actions in your own GitHub account, so you do not install Android Studio or the Android SDK. You do need a free GitHub account and a GitHub token.
You get a signed APK and an AAB. The AAB is the format Google Play asks for, but you upload and publish it yourself and the store’s own review rules apply to you.
Yes, either by capturing screens from your HTML app or by styling screenshots you provide. See App Store screenshots.