NewFlutter pack included. More stacks planned.

From idea to App Store and Play Store, one gate at a time.

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

Try it

Click a stage to see what runs and what you decide. Hit Approve to move on.

Your pipeline

10 stages, 10 gates

Stage 1with researcher

Research

Skills it runs

store-competitor-teardownreview-miningreddit-signal-miningmarketing-teardownidea-scorecard

Writes

01-research/competitors.md01-research/review-mining.md01-research/report.md
Approved

Your call

Build it or not

Santa Radar, a real runBuild. Score 6.6 out of 10, “build with a sharper wedge”: the Santa tracker made for grown-ups. See it live on the App Store

Every competitor targets parents of young kids. Incumbents fail on Dec 24 reliability, ads and paywall bait.

Stages 1 to 5

Plan before you build.

Nothing gets coded until you have approved the research, the spec, the design and the plan.

Gate G1 · ResearchSanta Radar
6.6/ 10
Build with a sharper wedge
Build. Score 6.6 out of 10, “build with a sharper wedge”: the Santa tracker made for grown-ups.
Every competitor targets parents of young kids. Incumbents fail on Dec 24 reliability, ads and paywall bait.
  • Research

    Store teardowns, review mining and Reddit signal, ending in a score and a go or no-go.

  • MVP spec

    An interview where you make every product decision, each with evidence and a recommendation.

  • Design

    Three visual directions as real mockups. You pick one and it locks into tokens.

  • Build plan

    Phases small enough to review, with the never-cut core in version one.

The team

Eight agents. One lead. You decide.

Each agent owns a stage. The main session is the lead: it hands out the work and runs every gate.

Stage 1

Researcher

Competitors, reviews, demand and the score.

Stages 2, 3

Product lead

Competitor flows, requirements, tech and analytics plan.

Stage 4

Designer

Moodboard, user journey, directions and the design system.

Stages 5, 6

Builder

The build plan, project setup, then one phase at a time.

Stages 6, 7

QA

Walkthroughs, UX audit and the design-quality scan.

Stage 7

Release gate

Checks the store rules. Can refuse a release.

Stage 8

Store launcher

Keywords, listing, screenshots, store setup and release.

Stage 10

Growth

Launch plan, monitoring, reviews and the next version.

Stages 7 and 8

Ship to both stores.

App Store Connect, Google Play, listings, keywords and the release build. Each one is a skill, not a guess.

  • A gate that can say no

    The release-gate agent checks store rules and can refuse a release before the stores do.

  • Listing and keywords

    Keyword research, listing text, icon and screenshots, localised.

  • Store setup, both sides

    Step-by-step skills for App Store Connect and Google Play.

  • Nothing irreversible without a yes

    Store submissions and paid cloud resources always wait for you.

Release checklist7 skills
store-compliance-check
aso-keywords
store-listing-assets
store-setup-ios
store-setup-android
release-build
beta-testers

It remembers

Stop any day. Pick up the next.

Every decision lands in a file in your repo. The next session reads it and carries on.

.product/decisions.mdSanta Radar
G1Build. Score 6.6 out of 10, “build with a sharper wedge”: the Santa tracker made for grown-ups.
G2Approve prd.md as written: a paid one-time unlock, no ads, no trial. Pricing was reworked at G9 into weekly, yearly and lifetime.
G3Approve requirements and analytics. Christmas Eve features run on the device.
G4Direction C, revised as “North Pole Poster”. Locked in tokens.json.
  • One file is the record

    Chat is not the record. Every gate outcome is written down, in order.

  • Lessons carry over

    The retro saves what worked. The next app reads it before it starts.

  • Updates never touch them

    Your lessons stay put. Any pack file you edited is backed up first.

How it starts

Get started in three steps.

No new app to learn. It runs in the coding agent you already use.

1

Install it

One command adds the pipeline to your project.

npx getmobilekit install --key YOUR_LICENSE_KEY
2

Describe your idea

The lead asks a few questions and writes down your idea.

/new-app a Santa tracker
for grown-ups
3

Approve each gate

Say yes, ask for changes, or kill it. Come back any day.

/continue-app
G1 approved · next: MVP spec

In the box

More you will use every day.

58

58 skills

Stage skills for each step, plus standards for onboarding, paywall, settings, sign-in and design quality.

/new-app

7 commands

Start, resume, check status, re-run a stage, run the retro, check store compliance and plan marketing.

Flutter pack included

Setup, coding standards, Firebase for the backend and RevenueCat for purchases.

doctor

A doctor command

Lists the tools each stage needs and which ones are missing on your machine.

Safe updates

Run update. Your lessons are never touched, and edited files are backed up first.

Yours to run

It runs inside your own coding agent, with your own store accounts.

Compared

vs a blank chat.

A coding agent can write code. It does not run a product process. This does.

A blank chat
MobileKit
Where it starts
Wherever the chat happens to
Research, then a go or no-go
Who decides
Whatever the model picked
You, at every gate
Memory
Gone when the chat ends
decisions.md, in your repo
Design
Generic defaults
Three directions, you pick one
Store launch
Figure it out yourself
App Store Connect and Play skills
Next app
Start from zero
Lessons carry over

Pricing

Pay once. Get everything.

One product, one payment. The first 10 people get $67. The next 20 get $87. After that it is $119.

Launch price

One-time payment. Yours to keep.

$67
$119
0 of 10 launch seats claimed10 left
Get MobileKit Rises to $87 once the launch seats are gone. 7-day money-back guarantee, no questions asked. How it works

Everything included

  • The pipeline: 10 stages and 58 skills
  • 8 agents and 7 commands
  • The Flutter stack pack and scripted cloud setup
  • Installer with install, update and doctor
  • The Santa Radar worked example
  • A lessons folder updates never overwrite

Questions, answered.

The short answers, before you buy.

What do I need to run it?

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.

How do I get it after I buy?

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.

What do I need besides the pack?

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.

What is not included?

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.

Which stacks does it build on?

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.

Does it build the app without me?

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.

Can I stop and come back later?

Yes. Every gate outcome is written to .product/decisions.md in your repo. /continue-app reads it to find its place, on any day.

Can I get a refund?

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.

How many apps can I build, and can I share it?

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.

How do updates work?

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.

Is MobileKit affiliated with Anthropic, Apple or Google?

No. It is an independent product that runs inside your own coding agent and works with your own store accounts.

Your next app, one gate at a time.

Install it, describe the idea, and say yes when it is right.