storebound logo storebound

Desktop app · preview

storebound desktop

Every app and game you ship, on Google Play and the App Store, in one window: releases on both stores, catalog parity, listings, crash health, reviews and TestFlight. It drives the same open source storebound CLI, keeps store keys in the system keychain, shows a dry run before every change, and never presses Submit.

Looking up the latest release…

Already use the CLI? storebound desktop opens the app in your app folder, or prints the download for your system; storebound desktop --download saves the installer to ~/Downloads after checking its signature (it never installs anything).

All downloads

Every system, with checksums

The app updates itself from this site: each update is signed, and the app checks the signature before it replaces anything. It asks before installing.

Verify

Check a download yourself

  1. Checksum: shasum -a 256 <file> (macOS, Linux) or Get-FileHash <file> (Windows) must print the SHA-256 above.
  2. Signature: every file has a .sig next to it (the app's update key, minisign). With minisign: base64 -d <file>.sig > f.minisig && minisign -Vm <file> -x f.minisig -P <key>, with the public key RWQqOO/ZeIr3RBmolt/fx108m89QNEUndRTFrucjx0CBMoeFb7/xhrvW
  3. Or let the CLI do both: storebound desktop --download.

The npm package storebound stays the CLI, MCP server and agent skills; it does not contain this app. The app brings its own copy of the CLI.