/android-app-factory · iOS & Android app shipping — the public Play Store counterpart to site-to-ios-app

One prompt. A Play Store-ready app.

Android App Factory runs the whole native pipeline from a one-line idea or target keyword: Kotlin + Jetpack Compose scaffolding, a real core loop before any polish, Play Billing only when it won't block v1 review, Play Store screenshots and ASO listing copy sized to Play's character limits, a truthful Data Safety and content-rating pass, and a signed release through Play App Signing. Nothing ships without an explicit confirmation, and every rollout starts on internal or closed testing before production.

View skill folder Install options

"build me an Android app for this" /android-app-factory Ask in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
$ /android-app-factory build a habit tracker Keyword picked · Kotlin + Compose scaffold building Play Billing skipped for v1 · screenshots + listing drafted BUNDLE SIGNED · INTERNAL TESTING

Public install commands

Claude Code full pack

/plugin marketplace add JasonColapietro/suede-creator-skills
/plugin install suede-skills@suede

Claude Code project-level copy

git clone https://github.com/JasonColapietro/suede-creator-skills.git /tmp/suede-creator-skills
mkdir -p .claude/skills
cp -R /tmp/suede-creator-skills/skills/android-app-factory .claude/skills/

Codex installer

python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
  --repo JasonColapietro/suede-creator-skills \
  --path skills/android-app-factory

What it covers

  • 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.

Stop shipping on vibes.

/plugin install suede-skills@suede All install paths