/android-app-factory · iOS & Android app shipping; the public Play Store counterpart to site-to-ios-app
One prompt to a signed Android build. It will not press publish.
Give it a product idea or a target keyword and it runs the native pipeline: Kotlin and Jetpack Compose scaffolding, a working core loop before any polish, Play Billing, the Data Safety disclosure, signing, and the Play Console release. Every rollout starts on a testing track, internal or closed, and stops for your confirmation. Nothing reaches production on its own.
"build me an Android app for this"->/android-app-factoryAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /android-app-factory build a habit trackerKeyword picked · Kotlin + Compose scaffold buildingPlay Billing skipped for v1 · screenshots + listing draftedBUNDLE SIGNED · INTERNAL TESTING
Keyword-first product selection before any scaffolding, so the app is buildable to a term worth ranking for.
Native Kotlin + Jetpack Compose scaffolding by default; never a bare JVM module that can't produce an installable APK/AAB.
A working core loop (input, processing, structured result, history, saved set) before monetization or visual polish.
Play Billing added only when it won't block the v1 review flow; a free v1 is the default when it would.
Play Store screenshots, feature graphic, and listing copy authored to Play's exact character limits, not generic marketing copy.
A truthful Data Safety form and content-rating questionnaire matched to actual SDK and data behavior.
A ship gate before release: build, listing, screenshots, signing, and secrets are checked, and no keystore or service-account key is ever committed.
Public-safe defaults throughout: placeholder application IDs, gitignored service-account keys, no real package names or Play Console account IDs in outputs.
When to use it
The user wants to plan, build, or ship a native Android app from an idea, keyword, or existing spec.
The user asks something like "build an Android app for X" or "get this ready for the Play Store."
Preparing a Play Store listing, screenshots, Data Safety disclosure, or a signed release build.
NOT for iOS work; use site-to-ios-app for converting an existing site into an iOS app.
NOT for reviewing or grading an existing app's code; use suede-code-review instead of building something new.
Best prompt
Use $android-app-factory to plan or build a native Android app from keyword through Play Store ship gate.
Related skills
Pairs with site-to-ios-app, the public iOS counterpart that wraps an existing site instead of scaffolding a new native app. Both end in the same discipline every lane in this pack shares: no release without an explicit ship gate and an owner's confirmation.
Install this skill
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.