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.
We don't change what we don't notice
$0.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 Reflect On: Know self better: map the core Health & Fitness 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: Lack of personalization options for journaling
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited mood tracking features
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: In-app purchase barriers
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No social sharing features
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.
We don't change what we don't notice. Reflect On is a simple journal for the gap between what happens to you and what you do next. When something stirs you up — fear, doubt, anger, boredom, fatigue — you log it in a few taps. Pick the trigger, pick how you actually responded, set the intensity, and add a note if you want. That's it. The whole thing takes about fifteen seconds. Over time, the app starts showing you yourself. A trends chart of positive and negative responses across days, weeks, or months. A weekly summary on the home screen so you can see how the last seven days actually went, not just how they felt. A report you can pull for any date range, with your top stimuli, your top responses, your longest positive streak — the kind of view that turns "I've been off lately" into something you can actually look at. What you'll find inside: - **Quick logging.** A four-step entry — stimulus, response, intensity, optional note — designed so you can do it in the moment without losing the moment. - **Customizable lists.** The built-in stimuli and responses are a starting point. Add your own, hide the ones that don't fit. The app should sound like you, not like a textbook. - **Trends you can read.** A clean line chart with positive and negative responses side by side, plus best-streak and active-days insights so you have something to react to, not just data. - **Reports you can share.** Pick any range, see the breakdown, share a plain-text summary with a friend, a coach, a therapist, or just yourself. - **History that doesn't judge.** Browse, search, edit, or delete past entries. Backfill a moment you forgot. Change your mind about how you'd label something. - **Three quiet themes.** Calm, Sunset, or Pastel — pick the one that feels like a place you'd actually want to come back to. - **Your data, on your device.** Everything is stored locally. Export to a JSON file when you want a backup or want to move devices. Reflect On isn't trying to fix you. It's a mirror you check once a day, or once a week, or whenever you feel like checking. The work is yours. This just helps you see it.
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.