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.
WW2 Daily answers two questions
$1.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 WW2 Daily: map the core Reference 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 interaction and engagement features compared to similar apps
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Lack of multimedia content
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: No social sharing options
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Limited personalization options
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.
WW2 Daily answers two questions. What happened today in World War Two? Where did it happen? Show me a map! Flip through daily events leading up to and during the most deadly and probably most significant conflict in human history. Each page shows the date, a succinct description, a zoomable map for the event and a link to the a detailed Wikipedia article. After a particular event? Use the search button to find it. The data for WW2 Daily comes from the World War Two Timeline Project at Cannonade.Net. This is a community contributed project to collect time and place data for the war. You can come to the site to browse the timeline or even log in and contribute new data. The Timeline Project currently indexes over 500 data points with new entries being added daily. If a significant event isn't in the database yet, it soon will be.
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.