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.
Why did we create whoo?
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.
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 whoo - Meet Your Friends: map the core Social Networking 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: Users report difficulty in discovering new friends.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited user engagement features compared to competitors.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: In-app purchase features can be confusing.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Performance issues during peak usage times.
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.
Why did we create whoo? Hello new friends! We’re so happy to finally launch whoo, and are grateful to all those who helped us during our test run. We set out to make an app that was better than other location sharing apps on the market. There are many of them out there, yet we felt that they all lacked that certain something. But why is that? The answer is simple - they aren’t any fun! They look the same, and offer the same standard location sharing features. whoo is different from other apps. We believe it’s important to have fun, and so we’ve packed a lot of fun into whoo. But whoo isn’t just a fun app, it’s also sleek, easy-to-use, and addictive, and we’re sure you’ll agree! It’s never too late to start your adventure with us. See you on whoo! - the whoo team English translation by Maya Jones 【Subscription】 Feature to see who viewed your profile (1 month) 1 month $1.99month https://docs.google.com/document/d/e/2PACX-1vS4LByEe0iUT1klYh7-AWwPJHf1hltue8ml_fts1TnGY3mj1OxRdntlRHYfHqpfZQydUkxlYQ6U_oCb/pub
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.