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.
You're a curious little kitty with a big personality, on an adventure to find your way back home
Free · 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.
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 Little Kitty, Big City: 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
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
You're a curious little kitty with a big personality, on an adventure to find your way back home. Explore the city, make new friends with stray animals, wear delightful hats, and leave more than a little chaos in your wake. After all, isn't that what cats do best? Try Before You Buy: Download and start playing for free! After collecting and turning in 25 Shinies to Crow, you'll be prompted to buy the full game. 1. One in-app purchase 2. Full game unlocked- forever! 3. No subscriptions 4. All progress carries over to the full game Please note: Camera/AR features are not available in the free trial and require the full game unlock. Little Kitty, Big City on mobile may vary in content and presentation compared to versions on other platforms. DISCLAIMER: Little Kitty, Big City can be played on iPhone 11 and newer, iPhone XS and newer, iPhone 12 Mini and newer, iPhone SE 3 and newer, iPad Pro 10.5" and newer, iPad Air 4th Gen and newer, iPad 10th Gen and newer, iPad Mini 6th Gen and newer.
Written user reviews are not shown here. Check current App Store reviews >
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 character customization options
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: In-app purchases can be confusing
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Repetitive quests can become boring
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Performance issues on older devices
Validate with people who use this workflow before building.
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.