How the dashboard works, step by step — and how the APK builder's base template is credited.
By default every message goes to Gemini — it's fast and free once you've added a Gemini API key in Settings.
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.
Open Settings and add the keys for whichever features you want:
All keys are stored locally in your browser only — never on a server, because there isn't one.
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.
In Settings, paste the YouTube Client ID from your own Google Cloud project.
Sign in with the Google account that owns the destination channel — this happens directly with Google, not through us.
Once a video file is ready in the conversation, use the upload action to send it straight to your channel.