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.
Swim PB is used to keep a historical record of a swimmer's (or a group of swimmers') times.
$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 Swim PB: map the core Sports 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 analytics on swim performance
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: No social features to share achievements
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Inconvenient input methods for swim data
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Lack of customization for swim types
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.
Swim PB is used to keep a historical record of a swimmer's (or a group of swimmers') times. When a time for an event (e.g. 50 freestyle, Short Course Metres) is entered for a swimmer, the app compares the time to the one previously stored for this event and informs the user if the time is faster, slower or no time exists for the event. In addition to the list of all a swimmer's times, a list of the swimmer's current Personal Best times for all events can be shown (these times can also be sent out via email from the app). Plots of a swimmer's results over time can also be displayed. Targets can also be added (via the 'Swimmers' menu - 'Show Targets'). An example target might be 'IAG div 2 male age 12-13' which would contain the target times for all events for Irish Age Group, division 2, male ages 12-13. The required target for a swimmer would then be selected from a list in the 'Personal Best Times' view. For each event in the list, the relevant time would be shown from the target, along with the difference between the PB time and the required time for that event. List items (from the 'Swimmers', 'Targets' and associated times) can be re-ordered and deleted using the 'edit' button - to delete a swimmer or time, click the red icon to the left of the item, to drag a swimmer or time to another location in the list use the 'drag' bar to the right of the item. Individual times can be modified by selecting the required time from the list (without needing to select the 'Edit' button).
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.