The App Store is full of apps pulling $1M+ a year — and most of them are solving simple, repeatable problems. What if you could paste a few screenshots into Claude Code, reverse-engineer the whole thing, and start building your own version today? That’s exactly what this video walks you through.

Get the Free Prompt Guide

Want the exact two prompts — one to reverse-engineer any App Store app from screenshots, and one to start building it with Claude Code? I’ve put both in a one-page PDF you can keep open while you build.

Get the free $1M App Prompt Guide →

Why App Store Apps Are the Best Thing to Clone

The App Store already validates everything for you. An app with 10,000 reviews and a $9.99/month subscription is a proven market — someone found the problem, built the solution, and people pay for it. Your job isn’t to invent something new. Your job is to build a better, leaner version of something that already works.

Claude Code makes this possible without a dev team. You don’t need to know how the original app was built — you just need the screenshots and the right prompts.

Step 1: Find Your Target App

Start with a specific niche you understand — fitness, productivity, finance, content creation. Look for apps that:

• Have 4+ stars and at least a few thousand reviews
• Charge a subscription (monthly or annual — not one-time)
• Have a clear, repeatable core feature you can spot in the screenshots

Take screenshots of the main screens: the onboarding, the home screen, the core feature, and the paywall or subscription screen. You’ll paste these directly into Claude Code.

Step 2: The Reverse-Engineer Prompt

Open Claude Code in your Antigravity IDE, paste in your screenshots, and run this prompt:

“I’m sharing screenshots of [App Name] from the App Store. Analyze these screens and reverse engineer the app. Break down: (1) the core features and what problem each solves, (2) the navigation structure and user flow, (3) the monetization model you can infer, (4) the data structures likely powering each screen, and (5) the tech stack you’d recommend to build a lean version. Give me a full spec document I can use to start building.”

Claude will produce a detailed spec — feature list, data model, user flow, recommended stack. This becomes your blueprint.

For both prompts formatted and ready to copy, grab the free guide →

Step 3: The Build Prompt

Once Claude has the spec, use this prompt to start the actual build:

“Based on the app spec above, build a working MVP starting with the core user flow. Create: (1) the basic UI matching the navigation structure from the spec, (2) the data model you recommended, and (3) the primary feature — just enough to demo. Use [your tech stack] and keep the scope tight enough to complete in this session.”

Claude will generate the files, structure the project, and give you working code for the first version. You’re not building the full app — you’re building the first thing a user needs to experience so they understand the value.

Step 4: Iterate With Claude in the Loop

This is where the Antigravity + Claude Code combo shines. After the first build:

• Describe the gap: “The onboarding is missing a step — add a screen that asks for the user’s goal before showing the dashboard.”
• Fix problems conversationally: “The subscription screen isn’t showing the annual pricing — add it below the monthly option.”
• Add features from the spec: Work down the feature list one session at a time.

Each session, Claude has the project context. It builds on what’s already there instead of starting from scratch.

What You Can Ship

In a focused 2–3 hour session using this workflow, most creators in the Vibe Coding community are shipping:

• A working onboarding + core feature screen
• A basic data model with local storage or Supabase
• A subscription paywall (Stripe or RevenueCat)

That’s a submittable MVP — not a full product, but something real you can test with users and iterate on.

Start With the Prompts

The reverse-engineer and build prompts are the hardest part to get right. Too vague and Claude gives you a generic spec. Too prescriptive and you lose the analysis. The prompt guide includes both — tested and formatted so you can paste them directly.

Get the free $1M App Prompt Guide →

Want to go further? Check out Clone Any $800K App in 15 Minutes for the full 4-phase cheat sheet — and the YouTube Repurposer system if you’re ready to automate your entire content pipeline alongside your build.