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.
Did I already take my medication today?
$1.99
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 Taken Today: Pill Reminder: 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
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Did I already take my medication today? Taken Today answers that one question. Tap the button when you take your pill — it turns green and stays green until midnight. That's the entire app. Get your answer without unlocking anything. WHY IT'S DIFFERENT Most medication apps want an account, a schedule, and your medical history. This one wants a single tap. No sign-up, no subscription, no cloud — answering "did I take it?" never needed any of that. WHAT YOU GET • One large, easy-to-hit button • Home Screen and Lock Screen widgets • An optional daily reminder, plus a follow-up if you still haven't confirmed • Your last four weeks at a glance, so you can spot a pattern • Up to 3 medications, each with its own icon and reminder • Works completely offline ALSO GOOD FOR • Vitamins and supplements • Any once-a-day tablet you find yourself second-guessing PRIVACY, PROPERLY No account. No tracking. No analytics. No network requests at all. Your medication data stays on your iPhone because there is nowhere else for it to go. Taken Today is a memory aid, not a medical device. It does not offer medical advice, track dosages, or replace your doctor's instructions.
Written user reviews are not shown here. Check current App Store reviews >
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: Users often forget to take their medications on time.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Users may not find it easy to manage multiple medications.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of visual progress tracking can demotivate users.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Users may feel overwhelmed by complex settings.
Validate with people who use this workflow before building.
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.