Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
You bookmark a recipe
$2.99 · In-app purchases
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Recipe Catcher: map the core Lifestyle workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Limited recipe discovery options
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Difficult to manage subscriptions
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: No offline access to saved recipes
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Basic search functionality
Validate with people who use this workflow before building.
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
You bookmark a recipe. You screenshot another. Six months later you can't find either. The one you actually wanted is buried under five tabs you'll never open. Recipe Catcher fixes that. Tap Share in Safari, send the page to Recipe Catcher, and the title, ingredients, and steps are parsed into a clean card that lives in your library forever. iCloud keeps everything synced across iPhone, iPad, and Mac. No accounts, no ads. When it's time to cook, you've got the full recipe at your fingertips — without the 1,200-word headnote about a Tuscan childhood. HOW IT WORKS Catch a recipe — paste a URL, or share from Safari, Chrome, or any browser. Plan your week — schedule meals across breakfast, lunch, and dinner in the built-in planner. Build your grocery list — tap "Add to Cart" on any recipe, then send the cart to Reminders. Ingredients arrive pre-sorted by aisle (produce, dairy, meat, etc.) and labeled with which recipe each one's for. FEATURES Parse recipes from thousands of food blogs and publishers — JSON-LD structured data plus HTML fallbacks for stubborn sites Smart auto-categorization into Breakfast, Lunch, Dinner, Sides, Soups & Stews, Sauces, Snacks, Drinks, and Desserts Search and sort your catalog by name, date saved, or category Built-in weekly meal planner with one-tap "Add Week to Cart" Share recipes with friends — they receive a clean HTML card that works in any browser, with one-tap import for fellow Recipe Catcher users iCloud Drive sync — your recipes live as plain JSON files you can browse in the Files app Reminders integration with aisle-aware sorting and per-recipe ingredient tagging Universal across iPhone, iPad, and Mac via Mac Catalyst PRIVACY Recipe Catcher doesn't collect, sell, or share your data. No account to create, no analytics service, no tracking pixels. The only network requests the app makes are to the recipe pages you ask it to import. Your catalog lives in your iCloud Drive — yours, portable, and readable by any text editor if the app ever disappears. WHAT THIS ISN'T Recipe Catcher isn't a discovery app. It won't suggest recipes, show you what's trending, or try to teach you to cook. It's a personal pantry for things you've already found and want to come back to. If you cook a lot, save a lot of links, and lose half of them — this is for you. GOT A SITE THAT DOESN'T WORK? Most major recipe blogs and publishers parse cleanly. If you hit a recipe that doesn't import, drop a note via the support email — fixes usually take an hour. The parser is updated regularly as sites evolve their markup.
Written user reviews are not shown here. Check current App Store reviews >
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.