Your agent writes the app.
Binary ships it.
Six skills for Claude Code and Codex that run the entire App Store lifecycle: first submission, every update, screenshots, even rejections. From your terminal or agent app. No Xcode. No Figma.
› /status Slate 1.2 (build 7) build uploaded ✓ processed 11:42 release notes ✓ written from git log privacy labels ✓ unchanged screenshots 6.9" ✓ regenerated this morning screenshots 6.5" ✗ missing 2 of 5 One step from submission. Regenerate 6.5" set and submit? (y/n) › y driving simulator flow ✓ 5 captures, framed and captioned uploading to App Store ✓ via ASC API submitted for review ✓ 11:47 Status: Waiting for Review. I'll tell you when Apple moves.
AI collapsed the cost of building. Shipping still costs a week.
Claude writes your app in a day. Then you spend days in App Store Connect: certificates, provisioning, privacy forms, screenshot sets in three device sizes, metadata, the review queue. The gap between code done and Ready for Sale is now the slowest part of shipping an iOS app, and you pay it again on every update.
Binary closes the gap. Your agent already knows your app better than any form does. These skills let it do the shipping too, through Apple's official App Store Connect API, with your key, on your machine.
10×
faster from code done to submitted, versus clicking through App Store Connect by hand
4 min
to regenerate a full screenshot set, every device size, framed and captioned
0
browser tabs. Not one App Store Connect form filled by hand
Six skills. The whole lifecycle.
Every stage of an app's life on the store is a skill. You never need to know where you are in Apple's process. Your agent always does.
/create
once per app
The first-time ceremony, guided. Registers your bundle ID, generates certificates and your ASC API key, walks you through the few web steps Apple won't let an API do, and verifies each one before moving on.
/submit
first release
The form-filling marathon, automated. Privacy labels, age rating, categories, pricing, full screenshot sets, metadata. Assembled by the agent, shown to you for one confirm, submitted via API.
/update
every release after
The one you'll run twenty times. Bumps the version, archives, uploads, writes release notes from your git log, reuses everything already set, submits. Code change to Waiting for Review in one command.
/screenshots
whenever the UI changes
Drives your real app in the simulator with seeded demo data, captures every beat in every required device size, frames and captions them. UI changed? Run it again. The whole set regenerates.
/rejection
when Apple says no
Paste the rejection notice. Get the diagnosis, the resolution path, and a drafted reply to App Review, built from a playbook of real rejections that actually got resolved.
/status
anytime
Reads ground truth from the ASC API: build state, version state, review state, what's missing. Tells you the exact next step, then offers to run it.
App Store screenshots without Figma.
Screenshots are captures of your actual running app, not mockups that drift out of date. They regenerate in minutes, not afternoons, every time your UI changes.
The Figma way
- Design frame templates per device size
- Boot simulator, capture by hand
- Paste captures into frames
- Export 6.9", 6.5", iPad sets
- UI changed? Do it all again
- An afternoon, every release
The Binary way
/screenshots- Agent seeds demo data, drives the flow
- Captures, frames, captions, all sizes
- Uploads straight to App Store Connect
- UI changed?
/screenshots - Minutes, unattended
Official API. Your key. One confirm before anything irreversible.
Binary uses Apple's official App Store Connect API, the same one fastlane and CI services use. Your .p8 key stays on your machine. Nothing goes through anyone's servers. The agent does the work. You pull the trigger.
Not a demo. A workflow with shipped apps behind it.
Binary wasn't designed on a whiteboard. It's the extracted, cleaned-up workflow behind a portfolio of live App Store apps, refined across dozens of real submissions, updates, and yes, rejections.
?
?
One-time. Yours forever.
Launch price for the first 100 licenses, then it goes to $399. This is a workflow, not a service. No servers, no accounts, nothing metered. You buy it once and it lives in your repo.
$199 $399
one-time, not another subscription
- All six skills, the complete lifecycle
- The screenshot engine
- The rejection playbook, from real rejections
- First-submission setup guide: .p8 key, certs, the Apple ceremony
- Reference repo wired into a real app
- 12 months of updates as Apple changes things
14-day refund, no questions. If it doesn't ship your app, it costs nothing.
Questions?
The ones every careful developer asks before pointing an agent at their App Store account.
Is this allowed by Apple?
Yes. Binary drives Apple's official App Store Connect API, the same API fastlane, Expo, and every CI service use. You generate the key in your own App Store Connect account. Nothing scrapes, nothing spoofs, nothing violates the developer agreement.
How is this different from fastlane?
fastlane is a toolkit you configure and maintain: Ruby lanes, config files, a human babysitting CI. Binary assumes the operator is your agent. Skills are procedures Claude runs, adapts, and chains together with everything else it does, like writing the release notes, fixing the rejection, regenerating the screenshots. Nothing to configure, nothing to babysit.
Do I need Claude Code?
Claude Code or Codex CLI. Skills are an open format, plain instructions plus small scripts, so any agent that can read a skill file and run shell commands can drive them. Claude Code is the primary target and what every skill is tested against.
Is it safe to give an agent my App Store Connect key?
The key stays on your machine, scoped to the role you assign it in App Store Connect. Every skill shows a summary and requires your explicit confirm before anything irreversible: uploads, submissions, listing changes. And the skills are readable text. Audit exactly what they do before you run them.
What if Apple changes something and it breaks?
Two answers. First, because the operator is an agent following a procedure rather than a brittle script, small changes usually get absorbed on the fly. Second, your license includes 12 months of updates, and keeping Binary current with Apple is the job.
Why a one-time fee?
Because this is a workflow, not a service. There are no servers, no accounts, nothing metered. You buy it once, it lives in your repo, it's yours.