How the dashboard works, step by step — and how the APK builder's base template is credited.
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.
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.