CRT
710c3a53d0
README is a short front page (about 120 lines) with one real visual per section; every former section moved unchanged into docs/*.md with a docs/README.md index (journey, rejections, getting-started, commands, growth, studios, store-art, listing-languages, api, skills, mcp, safety, faq, project). The site tells the same story on one page: the teaser in the hero, real CLI output as text, the desktop app as a section with light/dark captures of eight screens and the per-system downloads (desktop/latest.json); /desktop/ redirects to /#download. New capture tools: tools/site-desktop-shots.ts (fixture-mode desktop frames) and tools/site-term-shots.ts (real CLI output as text and WebP). tests/docs-links.test.ts checks README, docs and site links resolve.
50 lines
3.7 KiB
Markdown
50 lines
3.7 KiB
Markdown
# FAQ
|
|
|
|
**Is it only for games?** No. It started with my game, but every command is about store records, not engines or
|
|
genres. `init --profile app` and `--profile subscription-app` give you templates for a utility app with accounts and
|
|
for a subscription app (Data safety, App Privacy, declarations, listing and screenshot copy), the `app` screenshot
|
|
style, account deletion and demo account checks, and subscriptions on both stores. Game-only advice (IARC game
|
|
questions, gameplay footage, ad mediation) is marked as such in the skills.
|
|
|
|
**Do I need Claude (or any AI tool)?** No. The CLI is a normal command and the skills are Markdown checklists you can
|
|
read yourself. The AI integrations are optional adapters generated from the same files.
|
|
|
|
**Does it fill the questionnaires?** The ones with an API, yes: Play Data safety (the whole form from `dataSafety` in
|
|
the config; the import replaces the form, so the config is the single truth), Apple age rating, content rights,
|
|
categories, price and availability, the export compliance answer and the App Review details. The stores have no
|
|
public API for Play's App content cards (IARC content rating, target audience, ads, advertising ID, app access,
|
|
government / financial / health / news) or for Apple's App Privacy labels. For those, `init` gives you prepared
|
|
answers (`store/declarations.md`, `store/app-privacy.md`, per profile: a utility app with an account, a subscription
|
|
app, or a free-to-play game with ads and IAP),
|
|
and the `store-declarations` skill has the exact clicks: an agent with browser tools can fill them in while you
|
|
watch, or you copy them in yourself. Either way the answers are your statements to the stores: change what does not
|
|
match your app, and the agent asks you whenever the code does not prove an answer. `validate` cannot see these
|
|
forms, so `store-preflight` lists them as a manual check.
|
|
|
|
**My app or game is Unity / Godot / Flutter / React Native / native, not web.** Screenshots and clips come from the iOS Simulator
|
|
(`ios-sim`), an Android emulator or device (`android-emu`) or a folder you fill with any tool; only the rendering of
|
|
the store images uses a headless browser. The store commands do not care about the engine at all: they work on
|
|
your AAB / build numbers and listing files.
|
|
|
|
**Is my store account safe?** storebound uses the official APIs with keys you create and can revoke, never your
|
|
password. Store writes are dry runs until you say otherwise, and the public steps (submit, release) stay with you.
|
|
Use an App Store Connect key with the App Manager role and a Play service account limited to your app.
|
|
|
|
**Why Bun?** One fast runtime with TypeScript, `fetch`, a test runner and a static server built in: no build step and
|
|
zero runtime dependencies. It needs Bun installed (it does not run on plain Node).
|
|
|
|
**Does it upload my video to YouTube?** No. Play only takes a YouTube URL, and uploading to YouTube needs your Google
|
|
account; `shots video` makes the file, you upload it and paste the URL into `play.video`.
|
|
|
|
**Can it run store experiments for me?** On the App Store, mostly: `apple ppo create / upload` builds a Product Page
|
|
Optimization test from your `shots` variants (treatments, locales, screenshots) and you start it (`apple ppo start`
|
|
asks first). Results per treatment are only shown in App Store Connect. Play store listing experiments have no API:
|
|
storebound renders and checks the variant images, you set the experiment up in Play Console.
|
|
|
|
**Does it answer reviews by itself?** No. It drafts one file per review, your agent helps write the replies, and only
|
|
the drafts you mark `approved: true` are sent, by you, after a confirmation. Replies that offer something for a rating
|
|
are refused.
|
|
|
|
---
|
|
|
|
[All docs](README.md) · [README](../README.md)
|