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.
A fan of 18XX board games? Not so much of the constant need for bookkeeping with regard to Train routes, earnings, dividends, asset worth, etc.? This app does the heavy lifting and allows players to concentrate on playing.
$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 Survey Party: map the core Entertainment 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 survey types compared to competitors.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: User engagement is low due to lack of notifications.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: No social sharing features.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Confusing user interface for creating surveys.
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.
A fan of 18XX board games? Not so much of the constant need for bookkeeping with regard to Train routes, earnings, dividends, asset worth, etc.? This app does the heavy lifting and allows players to concentrate on playing. Track player holdings & Company share prices. Keep the cash flowing and game turns & Phases rolling. Lay Tiles and Tokens, purchase Trains, collect Earnings, and issue Dividends. Analyse company prospects. Dig into each player's current & future net worth - all through a clutter-free and easy-to-use touch interface. Pass a match among players for an easy PBEM tournament. Publish your match configuration using a custom URL scheme. Capture and share a PDF snapshot of each step along the way to becoming the wealthiest Director among your peers. -- Supported 18XX titles (note that only a subset of specific game features might be implemented for some of them): 1800 1817 1824 1825 (all Units) 1826 1829 (South & North) 1829 Mainline 1830 (incl. variations & scenarios) 1835 1837 1841 (both editions) 1843 1844 (original & Mayfair edition) 1846 1848 Australia 1849 1850 1853 (both editions) 1854 (original & Mayfair edition) 1856 1858 1860 1861 1862EA 1865 Sardinia 1867 1869 (Alan Moon) 1870 1880 1881 1886 1889 1899 18AL 18CZ (base game) 18Dixie 18EU 18FL 18GA 18GB 18MEX 18Neb 18NY 18PA 18Scan 18VA Poseidon Steam over Holland
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.