CRT
d2ce185441
- one version: package.json's version is the desktop app's too (desktopVersion removed); tools/desktop-version.ts keeps the plugin manifests and the app's copies equal, desktop-release publish refuses another version, release order app first then npm publish; the unpublished desktop 0.1.0 candidate is noted in the docs and CHANGELOG - storebound desktop installs (per user, no admin: macOS DMG -> /Applications or ~/Applications, Windows NSIS /S, Linux AppImage + .desktop with the storebound:// handler), updates an older app, notes a newer one (downgrade only with --force), asks once ([Y/n], --yes, exit 3 without a terminal), opens on the folder; --dry / --json / --download; the install steps are pure plans (cli/lib/desktop-install.ts); the version's own manifest dl/<version>/latest.json - credentials: one store, the CLI's credential profiles in ~/.storebound/credentials; the desktop writes and reads them (profiles.rs, files 0600), moves old keychain accounts into profiles on first start, shows profiles the CLI made; precedence env > named profile > project file > default profile; config `account`, "account" in the project's credentials.json; storebound accounts list | import (dedup by key id / service account e-mail, key files copied 0600, project file keeps keystore and review contact, backup, --dry, never prints values) | use - app folders: one list ~/.storebound/projects.json shared by the desktop (registry.rs), storebound desktop, apps folders | add | remove, ws init and ws without a workspace file - desktop: notice when a folder pins another storebound version; storebound-desktop --version - tests: version drift, desktop decisions and per-OS plans, credential precedence and import, registry (TS + Rust), keychain migration and profile round trip (Rust), boot check with old keychain state and the new shared state |
||
|---|---|---|
| .claude-plugin | ||
| .codex-plugin | ||
| .cursor/rules | ||
| .forgejo/workflows | ||
| .github | ||
| apps/desktop | ||
| bin | ||
| brand | ||
| cli | ||
| docs | ||
| examples | ||
| media/teaser | ||
| site | ||
| skills | ||
| specs | ||
| templates | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .mcp.json | ||
| AGENTS.md | ||
| bunfig.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| gemini-extension.json | ||
| GEMINI.md | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.json | ||
storebound
From an empty folder to "Submit for review" on Google Play and the App Store.
Your AI agent does all of it with storebound: builds, uploads, store text, screenshots in every language and size, in-app products and prices, the compliance forms, even the consoles that have no API. You only press Submit.
Website: storebound.dev · Docs: docs/ · npx storebound init
Watch the teaser on storebound.dev: the demo game from an empty folder to both stores, then the desktop app.
Your agent does the whole job
Do it, don't ask. You ask once ("get my app ready for both stores"); your agent and storebound do the work:
the app records, builds and uploads, listings in every language, screenshots and previews in every store size, icons,
in-app products and subscriptions priced in 175 countries, Data safety, App Privacy, age rating and every other form,
and the console pages that have no API (the agent drives them from a console plan). Each step is planned first:
You press only the final public or irreversible buttons (Submit for review, releasing, App Privacy Publish, legal agreements) and answer, once and in one batch, the facts no file can prove. The full rules: AGENTS.md; the whole journey step by step: docs/journey.md.
You won't get rejected for the avoidable things
storebound scan reads your project (Xcode and Gradle files, manifests, lockfiles, SDKs, your listings) and the store
state, and names every App Review or Play policy problem it can prove before the stores do: the guideline, the
evidence as file:line, and the fix.
Every rule, what it proves and what only a reviewer can see: docs/rejections.md.
The desktop app: every app, both stores, one window
Every app and game you ship on Google Play and the App Store side by side: releases, charts, catalog and prices,
crash health, reviews, TestFlight and the rejection checks. Send for review from there too: a dry run first, then a
confirm, then your click. Same storebound underneath, same version number as the CLI, and the same store accounts
and app folders as your terminal (~/.storebound).
More screens: portfolio, growth charts, prices, checks, TestFlight, console plan
npx storebound desktop installs it for you (macOS, Windows, Linux; signature checked, no admin rights) and opens it on
the current app folder. Manual downloads: storebound.dev/#download. Internals: docs/desktop.md.
Works with your AI, safe by design
Skills, an MCP server and the CLI for Claude Code, Codex, Cursor, Gemini CLI, Copilot, Windsurf, OpenCode or
anything that reads AGENTS.md. Every write shows a dry run first; submit, release and delete are not MCP tools; keys
stay in env vars or the gitignored .storebound/.
Per-tool setup: docs/getting-started.md · MCP tools: docs/mcp.md · Safety model: docs/safety.md.
Install and start
You need Node 20+ or Bun 1.1+ (and ffmpeg for icons, screenshots and video).
cd my-app
npx storebound init # storebound.config.ts + .storebound/ in this project (--profile app | subscription-app | game)
npx storebound desktop # installs the desktop app once (asks first) and opens it on this folder
One product, installed once per machine: the CLI (npx / bunx) and the desktop app have the same version, the same
store accounts (~/.storebound/credentials, npx storebound accounts) and the same list of app folders. Each project
has its storebound.config.ts and a gitignored .storebound/ (upload keystore, review contact). Then
npx storebound install --agent claude (or codex, cursor, gemini, copilot, windsurf, opencode) and
npx storebound check. Every npx storebound ... works as bunx storebound ... too.
Then ask your agent: "take my app to Google Play and the App Store". Claude Code plugin, credentials, coming from fastlane: docs/getting-started.md.
What it covers
Store screenshots of the demo game, rendered by storebound in every size and language:
- The journey: every step from setup to Submit, what is API, what the agent drives in a console, what stays yours
- Rejection scan: every rule with its App Store guideline or Play policy
- Commands: the full command reference
- Store art: screenshots, fonts, previews, variants
- Growth extras and console forms: PPP prices, Apple Ads, web presence, RevenueCat,
console plan/console fill - Many apps, release trains, workflows · Listings in more languages · Every API endpoint
- Skills · MCP server · Safety model · Idempotency · Pitfalls
- Desktop app · Desktop releases · FAQ · Roadmap, contributing, credits
Contributing and license
Issues and pull requests are welcome; see CONTRIBUTING.md (bun run ci must be green).
MIT, see LICENSE. Copyright (c) 2026 CRTkafa. Not affiliated with Google or Apple.