This page is for developers and founders getting ready to submit to Google Play and the App Store. You will draft the answers the stores ask for and check your screenshot sizes. Nothing is uploaded and no store account is touched.
shipvo store details --dry-run [--out dir] drafts what Google Play and the App Store will ask, from shipvo.json. This is slice 1 of the store work (#249): it only writes files. Nothing is uploaded and no store credentials are read. Without --dry-run the command exits 2 with "upload is not available yet; use --dry-run".
What it reads
The capabilities in listing.capabilities in shipvo.json. Names match @shipvo/device.
| Capability | Data safety row |
|---|---|
camera | Photos |
location | Precise location |
contacts | Contacts |
calendar | Calendar events |
files | Files and docs |
payments | Payment info |
notifications | Device or other IDs |
biometrics, share, clipboard, network | none |
Any other capability is listed as a question for you. It is never dropped.
What it writes
data-safety.csv: the derived answers in the Play Data safety import layout. With no data-touching capability, the CSV leaves out the "collects data" answer: sign-in or third-party SDKs may still collect data. Check the column and response ids against the template you export from Play Console before you import.privacy-policy.md: a draft that names only what the app declares. Review it before you publish. It is not legal advice.
The command prints "Filled without you: x of y fields". That counts only the derived Data safety rows, not the questions list, so it does not mean you are done.
It also prints the questions it cannot answer: whether each data type is shared, third-party SDKs, sign-in, data deletion and a contact address.
Privacy policy
shipvo store policy [--out dir] [--strict] writes privacy-policy.md and privacy-policy.html (default folder .shipvo/store). Each data use in the text comes from a capability in shipvo.json; questions the app cannot answer are listed under "Still to confirm". Set the publisher and contact in shipvo.json:
{ "listing": { "privacy": { "company": "Acme Ltd", "contactEmail": "privacy@acme.example" } } }The command prints the fields still missing. With --strict it exits 1 while any is missing. Review the files and host the page yourself; the command never uploads anything.
Store setup and status
shipvo store setup and shipvo store status (slice 2 of #249) tell you which accounts to open and what to do next. They make no store calls and read no credentials.
shipvo store setup --company no
shipvo store status
shipvo store status --mark play-account
shipvo store status --mark apple-account --as waitingsetup asks if you have a registered company. In a terminal it asks questions. For agents and CI, pass flags: --company yes|no, --android-now, --play-account-before-2023-11-13. With no flags and no terminal it uses the default: no company. A bad flag value exits 2. It writes store-plan.json.
| Situation | Google Play | App Store |
|---|---|---|
| Registered company | Organization account, no tester rule | Organization account (D-U-N-S) |
| No company (default) | Personal account: 12 testers opted in for 14 days in a row before production | Individual account |
| No company, needs Android now | Same as above. There is no faster route yet; the output says so | Same as above |
| Play account made before 13 Nov 2023 | Exempt from the tester rule | Same as above |
The tester rule is shown only for personal Play accounts that are not exempt. Apple has no such rule.
status reads store-plan.json and prints one timeline per store. Each step is todo, waiting or done, followed by what you do next. --mark <step> sets a step to done; add --as waiting for a wait. With no plan file it says to run setup.
Get your 12 testers
A new personal Google Play account must have at least 12 testers opted in to a closed test for 14 days in a row before you can apply for production. Read Google's help page for the current rule. Organization accounts and personal accounts made before 13 Nov 2023 skip it.
shipvo store testers [--package id] [--track alpha] [--json] prints the steps for your app. store setup and store status show the same advice on the play-closed-test step.
- In Play Console, make a closed testing track and upload your first build by hand. Play does not let the API do the first upload of a new app.
- Add testers as Google Groups on the track: your own group, and
shipvo-testers@googlegroups.com(the Shipvo Testers group). - Share your opt-in link:
https://play.google.com/apps/testing/<package>. - Join Shipvo Testers at shipvo.dev/testers and test other founders' apps. The community works because everyone tests.
- Keep 12 or more testers opted in for 14 days in a row. If the count drops below 12 the clock resets.
Anyone can join Shipvo Testers. Members cannot see each other's emails, and only managers post. We cannot say how many testers will opt in.
To add the group through the API, pass your own Play service account key (it needs access to the app in Play Console):
shipvo store testers --package com.example.shop --play-key play-key.jsonThe command opens a Play edit, reads the groups already on the track, adds Shipvo Testers to them, and commits. It never removes a group. The key is read once and not stored. Without --play-key no network call is made.
Screenshots (fast mode)
shipvo store screenshots renders your app in the simulator and writes store-sized files. It prints "fast mode: simulator render, not the native UI". The simulator runs your web build in headless Chromium, so fonts, safe areas and native widgets can differ from a phone.
shipvo store screenshots # builds the app, starts the simulator, renders
shipvo store screenshots --sim http://localhost:4546 --out store-assets/rawIt renders the start screen and every entry in routes in shipvo.json (deep links, as for shipvo explore). It does this for each set: iPhone (1290x2796), iPad 13-inch (2064x2752), Play phone (1080x1920), Play 7-inch tablet and Play 10-inch tablet (both 1200x1920). Files go to store-assets/raw/<set>/NN-<screen>.jpg, in JPEG so there is no alpha channel. The extension comes from the checker's format result, not from the first byte. A file that is not a PNG or JPEG is kept as .bin and reported as failed.
Each file gets the checker result from @shipvo/store, then each set gets a count check. If a set takes fewer files than you have screens, the extra screens are skipped and the command says so. The exit code is 1 if any file fails. The Play feature graphic and icon are not app screens and are not made here.
Store mode (native capture on an emulator or simulator) is a later slice. Nothing is uploaded.
The size numbers come from the table in @shipvo/store and issue #249. They were not re-checked against the Apple and Play pages when this command was added. Check them before you submit.
Screenshots with marketing frames
shipvo store screenshots --mode frames turns each render into a store-ready image: a phone or tablet frame on a solid background with a short caption above it. Android sizes get an Android-style frame and iOS sizes get an iPhone or iPad-style frame, in the same layout, for Android and iOS together.
shipvo store screenshots --mode frames # writes store-assets/frames/<set>/NN-<screen>.png
shipvo store screenshots --mode frames --out my-frames --jsonFiles are PNG with no alpha channel, at the exact sizes from the table above, and each one goes through the same checker. Captions come from store.captions in shipvo.json, keyed by route or screen name:
{ "store": { "captions": { "start": "Plan your day on the water", "tide://cart": "Pay in one tap" } } }With no entry, the caption is the screen title (the app name for the start screen). A long caption wraps at spaces; if it is still too long it is shortened at a word boundary and ends in "...". Words are never cut in the middle: the text shrinks first, and a caption that cannot fit is shown as "...".
With --json, stdout carries one envelope. Its data is { ok, mode, out, files: [{ set, file, ok, problems }], notes }, and the progress lines go to stderr.
See the package: packages/store.
Troubleshooting
upload is not available yet; use --dry-run (exit 2). Upload is not built. Add --dry-run.
A screenshot fails the checker (exit 1). The command lists the files that failed. Fix those files, then run it again. Check the sizes against the store pages before you submit.