Tutorial

step 1

Install & run the demo

Prerequisites: Node.js ≥ 20.12 and pnpm ≥ 9.

$ git clone https://github.com/dioKR/storepulse.git
$ cd storepulse
$ pnpm install
$ pnpm demo

The demo board uses sample data shaped like a real team — two apps, each with a prod and dev variant, on both platforms. Every badge you'll ever see is in it: LIVE, 50% (staged rollout), REVIEW, REJECTED, draft.

step 2

List your apps

$ npx storepulse init

Works in any folder — it creates storepulse.config.json and a .env template (existing files are never overwritten) and git-ignores the credential files. In a clone of this repo, cp storepulse.config.example.json storepulse.config.json does the same. Now open storepulse.config.json and list your apps:

step 3

Apple — App Store Connect API key

From here on you're filling in the .env that storepulse init created (repo clone: cp .env.example .env).

1. App Store Connect → Users and Access → Integrations → App Store Connect API
2. Under Team Keys, click ＋. Role: Developer is recommended — it covers everything storepulse reads. App Manager works too, but a leaked App Manager key can submit apps and edit metadata, so grant the least privilege you can.
3. Download the .p8 file. Apple allows exactly one download — keep it safe (storepulse init git-ignores it for you). This key can write as much as its role allows — if it ever leaks, revoke it immediately in App Store Connect.
4. Fill in three values:

ASC_KEY_ID=ABC123DEFG          # "Key ID" column of your key
ASC_ISSUER_ID=xxxxxxxx-...     # "Issuer ID" at the top of the page
ASC_PRIVATE_KEY_PATH=./AuthKey_ABC123DEFG.p8

Console menus move around from time to time — if they have, follow Apple's official guide: Creating API Keys for App Store Connect API.

step 4

Google — Play service account

1. In Google Cloud Console, pick (or create) a project and enable the Google Play Android Developer API.
2. IAM & Admin → Service Accounts → create one (no roles needed) → Keys tab → Add key → JSON.
3. In Play Console → Users and permissions → Invite new users → paste the service account email (…@…iam.gserviceaccount.com) → grant View app information on your apps. Grant only that — never give the service account any Release/publish permissions; storepulse doesn't need them, and a leaked key stays read-only.
4. Point .env at the JSON:

PLAY_SERVICE_ACCOUNT_PATH=./service-account.json

If the console layout has changed, Google's official guide covers the same steps: Getting started with the Google Play Developer API.

step 5

Run

$ npx storepulse

Your real board appears (in a clone of this repo, pnpm status does the same). Rows with credential problems show an inline error — they never hide the rest of the board.

step 6

See it in a browser

$ npx storepulse serve

Open http://127.0.0.1:4780 — the same board, same design, as an auto-refreshing web dashboard. Click any row to expand a detail panel with full release notes, dates, and a TestFlight expiry countdown. The chips at the top filter the board by OS and group. Click a state badge (not the row) to open a dialog explaining what that state means, and flip the UI between English and Korean with the EN/KO switcher in the header — your browser remembers the choice. No credentials yet? npx storepulse serve --demo works too. It binds to 127.0.0.1 by default: the board may list unreleased versions, so keep it local.

step 7 — optional

Link Expo (EAS) builds

Ship with Expo? Add an access token to .env (create one at expo.dev → Access tokens; for organizations, prefer a View Only robot token — storepulse only reads builds and submissions) and give each Expo app in storepulse.config.json its easProjectId (app.json → extra.eas.projectId):

EAS_TOKEN=...

The snapshot JSON and the web dashboard's detail panel now show which EAS build each store version came from — commit, build profile, submission status (the terminal board keeps its summary) — and npx storepulse doctor verifies the whole EAS chain in its [5] section.

troubleshooting

When something's off

First, run npx storepulse doctor — it diagnoses most of the causes below automatically, with a one-line fix for each.

Still stuck? Open an issue — include the exact error line from the board.