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.
Dominate the world
$4.99
Evidence scope: #77 is the current overall US Paid chart position. 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.
Your first Build Kit is free with a verified email.
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 Strategery: 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 modes can become repetitive.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: No social features to connect with friends.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of tutorials for new players.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Some users report bugs during 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.
Dominate the world. One blob at a time. World domination isn't a very fashionable ambition these days, but that doesn't mean you can't pretend. Strategery is a battle between your pegs and the green, orange, blue, and red blobs that dare to stand in your way. It's also a little bit of App Store history. Strategery first launched in 2008, back when the App Store was barely a few months old. Macworld named it the Best Strategy Game of 2009. Slate called it their latest iPhone gaming habit. Daring Fireball said the gameplay had a great feel. And a Macworld reviewer named Lex Friedman wrote that there was no game he played on his iPhone more. That reviewer now makes Strategery. Life is funny. HOW IT'S PLAYED The world is made of blobs. Every blob holds pegs — your pegs, ideally. Pick a blob you own, point at a neighboring blob you don't, and roll. More pegs, better odds. Win the roll and the blob changes color. Lose it and, well, you still have your other blobs. Keep going until the whole map is your color and everyone else is looking for the rematch button. Your turn, your dice, your questionable decisions Bigger stacks of pegs win more rolls. Usually. Every blob you hold earns you more pegs Last color standing dominates the world. Politely. THREE WAYS TO CONQUER Solo: Play against the computer. It has no friends, no feelings, and no plans this evening. It will happily lose to you all night. (Or not. You choose how clever it gets to be.) Online: Play against your friends. Take turns from wherever you are. A push notification lets you know when it's your move, or when someone has done something regrettable to your blobs. Pass and play: One phone, one couch, several rivals. Hand it over, let them try, and try not to gloat. CLASSIC OR CHAOS Classic is the game you remember: dice, blobs, and your own poor judgment. Chaos adds starred blobs. Capture one and the wheel spins. Your conquest has consequences. Either way, you pick how much world there is to dominate. A WAR WITH NO CASUALTIES Blobs don't bleed. Pegs don't feel pain. Nothing explodes, nobody gets hurt, and the only thing that ever gets conquered is a colorful shape on a map. Somebody's pride may be wounded when you take their last blob, but that's between the two of you. For iPhone and iPad. Contains no violence, several dice, a healthy number of blobs, and a reasonable amount of whimsy. Strategery was originally designed by Sumul Shah, Courtland Idstrom, and Peter Ju. This version comes from Lex Friedman, who is one person and would be delighted by a rating or review. It's not strategy. It's Strategery.
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.
Not assessed in a Build Kit yet.
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.