Stage 1
Researcher
Competitors, reviews, demand and the score.
NewFlutter pack included. More stacks planned.
MobileKit turns your coding agent into a small product team. It researches, specs, designs, builds and launches your app, then stops for your yes at every step.
Pay onceWorks inside Claude CodeYou approve every gate
Click a stage to see what runs and what you decide. Hit Approve to move on.
Skills it runs
Writes
01-research/competitors.md01-research/review-mining.md01-research/report.mdYour call
Build it or not
Every competitor targets parents of young kids. Incumbents fail on Dec 24 reliability, ads and paywall bait.
Stages 1 to 5
Nothing gets coded until you have approved the research, the spec, the design and the plan.
Store teardowns, review mining and Reddit signal, ending in a score and a go or no-go.
An interview where you make every product decision, each with evidence and a recommendation.
Three visual directions as real mockups. You pick one and it locks into tokens.
Phases small enough to review, with the never-cut core in version one.
The team
Each agent owns a stage. The main session is the lead: it hands out the work and runs every gate.
Stage 1
Competitors, reviews, demand and the score.
Stages 2, 3
Competitor flows, requirements, tech and analytics plan.
Stage 4
Moodboard, user journey, directions and the design system.
Stages 5, 6
The build plan, project setup, then one phase at a time.
Stages 6, 7
Walkthroughs, UX audit and the design-quality scan.
Stage 7
Checks the store rules. Can refuse a release.
Stage 8
Keywords, listing, screenshots, store setup and release.
Stage 10
Launch plan, monitoring, reviews and the next version.
Stages 7 and 8
App Store Connect, Google Play, listings, keywords and the release build. Each one is a skill, not a guess.
The release-gate agent checks store rules and can refuse a release before the stores do.
Keyword research, listing text, icon and screenshots, localised.
Step-by-step skills for App Store Connect and Google Play.
Store submissions and paid cloud resources always wait for you.
It remembers
Every decision lands in a file in your repo. The next session reads it and carries on.
Chat is not the record. Every gate outcome is written down, in order.
The retro saves what worked. The next app reads it before it starts.
Your lessons stay put. Any pack file you edited is backed up first.
How it starts
No new app to learn. It runs in the coding agent you already use.
One command adds the pipeline to your project.
The lead asks a few questions and writes down your idea.
Say yes, ask for changes, or kill it. Come back any day.
In the box
58 Stage skills for each step, plus standards for onboarding, paywall, settings, sign-in and design quality.
/new-app Start, resume, check status, re-run a stage, run the retro, check store compliance and plan marketing.
Setup, coding standards, Firebase for the backend and RevenueCat for purchases.
doctor Lists the tools each stage needs and which ones are missing on your machine.
Run update. Your lessons are never touched, and edited files are backed up first.
It runs inside your own coding agent, with your own store accounts.
Compared
A coding agent can write code. It does not run a product process. This does.
Pricing
One product, one payment. The first 10 people get $67. The next 20 get $87. After that it is $119.
One-time payment. Yours to keep.
The short answers, before you buy.
A coding agent that reads a .claude/ folder (MobileKit is built for Claude Code) and Node 18 or later for the installer. After installing, run doctor: it lists the tools each stage needs and which are missing on your machine.
Dodo Payments emails you a license key. Run npx getmobilekit install --key YOUR_LICENSE_KEY in the folder where your app will live. The installer checks the key, downloads the pack and installs it. You do not need a GitHub account. The key works on up to 3 of your machines, and npx getmobilekit update fetches new versions.
A Mac with Xcode for iOS builds and store screenshots, Python 3 and Google Chrome for the research and design scripts, and your own paid Apple Developer and Google Play accounts. Generated store screenshots use an OpenAI API key, billed to you by OpenAI. The default Flutter stack uses Firebase, and cloud functions and AI features need a billing-enabled Firebase project. A new personal Google Play account must run a 14-day closed test before it can publish. Reddit research works best with a free Reddit API key, which you create yourself. Run doctor to see what is missing on your machine.
App code you did not decide on: the pipeline builds what you approve at each gate. No stack other than Flutter yet. Store submission, which stays your explicit yes. Legal pages are drafts, not legal advice. No done-for-you service, and no promise of downloads or rankings.
Research and the spec name no framework. A stack is proposed before the requirements and confirmed at gate 3, and the build stages use a stack pack. The Flutter pack is included, with Firebase for the backend and RevenueCat for purchases. Flutter is the only pack so far.
No, and that is the point. After each stage the lead stops at a gate and you approve, ask for changes, or kill the idea. In stage 2 it interviews you on every product decision. Anything that cannot be undone, like a store submission or a paid cloud resource, needs your explicit yes.
Yes. Every gate outcome is written to .product/decisions.md in your repo. /continue-app reads it to find its place, on any day.
Yes. You have 7 days from purchase to ask for a full refund, with no questions asked. Email us from your purchase address with your order number. The refund page has the steps, what is covered, and how double charges are handled.
As many apps as you want, for yourself, your employer or clients. You cannot share, resell or publish the pack: one licence is one person, and each teammate needs their own. The apps and documents you make with it are yours.
Every update to the major version you bought is included. Run the update command. Your lessons in .claude/learnings/ are never touched, and any pack file you edited is saved to .claude/.pack-backup/ before it is replaced.
No. It is an independent product that runs inside your own coding agent and works with your own store accounts.
Install it, describe the idea, and say yes when it is right.