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.
The decade is 1990
$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 The Completionist: 1990 – 1999: map the core Games 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 game variety can lead to boredom.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: In-app purchases can be confusing for users.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of social interaction features.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Potential for repetitive gameplay.
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.
The decade is 1990. Your zine has a circulation of zero and a GeoCities page with a broken hit counter. You have opinions about Tarantino, a 14.4 modem, and just enough cash for one print run. Build a pop culture magazine from nothing. Hire writers, editors, and researchers. Commission stories about the movies, music, games, and news that shaped the 90s. Move work across a Kanban board from pitch to published. Watch your operation evolve from photocopied zines at Kinko's to a real media company with a .com domain and a homepage that loads in under 8 seconds. Try not to go broke before the IPO. Part strategy game. Part idle. Part workflow sim. Part love letter to the decade that broke the internet. WHY YOU'LL LOVE IT • Your Choices Matter — Specialists or generalists. Deadlines for bonus pay or slow burns for 5-star quality. Hire fast and spend thin, or run lean and invest in iMacs and Aeron chairs. Prestige early for a few legacy points, or grind deep for the full haul. Every run asks a different question. • Windows 95 Aesthetic — Beveled chrome, tiled wallpapers, system fonts. Looks like running Netscape Navigator on your parents' Compaq. In a good way. • In-Game Achievements — On top of Game Centre achievements, more homage to the 90s. • Events and Multipliers — Random events from the 1990s that boost (or tank) your revenue mid-run. • Easter Eggs — Can you find the flying toast? The Konami input code? The dial-up modem? • IPO — Take a chance at the big time, but if your stock tanks... Godspeed, old friend. • Thousands of 1990s Headlines — Jurassic Park opening weekend. Nirvana knocking Michael Jackson off #1. The O.J. trial. Pokémon. Y2K panic. The stuff that shaped a generation. • Kanban Workflow — Research, draft, create, edit, publish. Manage stories across the board like a project manager who's really into Radiohead. • Build Your Team — Creators write. Editors catch typos. Researchers break leads. Managing Editors keep the whole operation from imploding. Hire smart, level up skills, equip your crew with Power Macs, standing desks, and Discmans. • Prestige System — Hit $500K and complete a Volume. Start your next run with permanent legacy upgrades that pull your strategy in new directions. Revenue Boost or Inflation Shield. Quality Boost or Fast Learners. There's no correct order. There's your order. • Speed Boosts — Frappuccinos, Surge soda, Snapple. The fuel of journalism. Consumables for a temporary push. A Bull Terrier for permanent motivation. Or upgrade your dial-up to a T1 Line. • Analog to Digital — Watch your magazine evolve from paste-up zines to a full online publication. Your arc mirrors the decade's defining shift. • NO ADS. NO ENERGY GATES. One optional speed boost. That's it. The first Volume teaches you the ropes. Volumes 2 through 10 are where you figure out what kind of editor you actually are.
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.