Indie
For your first app.
- 1 app
- 15 builds a month
- iOS and Android
- Store listing written for you
- Rejection fixes included
Tab bar, Face ID, push and an offline screen, added around your code. Then built, signed and published to the stores for you.
On a phone, a website has an address bar, no tab bar and a blank page offline. StoreReady adds what a real app has, around your code. Your project stays exactly as it is.
Apple turns down apps that are only a website (guideline 4.2). This is the difference its reviewers look for.
It reads the log, fixes what broke in your project and builds again. Those fixes stay for every next build.
Plain-words explanation, the changes made, resubmitted.
Every size both stores need. Edit anything.
Turn on automatic builds and every push to your branch builds a new version and sends it to the store.
Add StoreReady to Claude Code, Codex or Cursor once. Then ask it to publish your app, or to sort out a store rejection.
claude mcp add -s user storeready -- npx -y @storeready/cli mcpcodex mcp add storeready -- npx -y @storeready/cli mcpCursor and other tools: the setup is on the AI tools page once you sign in.
Every plan includes iOS and Android, your store listing, and rejection handling. Cancel any time.
For your first app.
For makers with a few apps.
For agencies shipping client apps.
Shipping a lot this month? Add extra builds anytime, from $3 a build. They never expire.
No. A wrapper shows your website in a frame, and Apple turns those down (guideline 4.2). StoreReady adds what a phone app has and a website doesn’t: a tab bar, a Face ID or fingerprint lock, haptics, push notifications, an offline screen, the share sheet and Android’s Back button. Your code stays as it is.
Yes. No package.json and no build step needed. Your pages, styles and images go into the app as they are, with the same native features as any other app.
Yes. Apple publishes every app under its owner’s own developer account (Apple charges $99 a year for it, and Google Play has a one-time $25 fee). We walk you through both, step by step, during setup.
Apple reviews every app, so nobody can promise approval. What we can do: add the native features reviewers ask for before you submit, and if Apple says no, explain why in plain words, fix it and resubmit.
No. Keep building in Lovable, Bolt, Replit, v0, Cursor or Claude Code, or keep editing your HTML, the way you do now. We read your project as it is and add the app layer around it.
Our build assistant reads the log, fixes what broke in your project and builds again. Its changes are kept for your next builds, and you can pull them into your own code with one command.
Yes. Add StoreReady to your AI tool with one command, then ask it to publish the app. It sets the app up, starts the build and tells you when it is done.
Push your changes to GitHub and a new build starts by itself, or start one yourself in a click. We build, sign and send the update to the store, and your users get it like any other app update.
You do. It’s published under your Apple and Google accounts, with your name on the listing.
Your keys are encrypted and only used to build, sign and upload your apps. You can revoke them from App Store Connect or Google Play Console at any time.