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.
App Overview
Names in a Hat
Have you ever needed to randomly pick names out of a hat and not have the necessary materials to do so? I've heard the scenario all too many times
$0.99 · In-app purchases
PRICE
$0.99
In-app purchases
BUSINESS MODEL
Paid
No overall Grossing estimate available
RATING
★ 4.6
132 ratings · Top 15%
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.
Build your own version
Build Kit
Make this idea yours
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Add to a Remix
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
Make it yours Optional
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
What's included16 files
A product spec, phased build plan, differentiation notes, and screen references.
- START_HERE
- AGENTS
- EVIDENCE
- SPEC
- BUILD_PLAN
- DIFFERENTIATION
- skills/
- screens/
Preview a sample Build Kit No email needed
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Screen plan
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.
Differentiate and validate
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.
Free quick prompt For a smaller starting point
Quick prompt
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
// RORK SYSTEM PROMPT
Rork plan preview for Names in a Hat: map the core Utilities 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.
Continue in Rork >
Affiliate link: CloneChart may earn a commission at no extra cost
Opportunities
AI-GENERATED OPPORTUNITY HYPOTHESES
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
Implement sorting/filtering features for better name management.
Assumption to check: Users want more customization options for names (e.g., sorting, filtering).
Validate with people who use this workflow before building.
Hypothesis 2
Enhance UI with better graphics and animations.
Assumption to check: Some users may find the interface too simple and lacking visual appeal.
Validate with people who use this workflow before building.
Hypothesis 3
Extend sharing capabilities to include social media options.
Assumption to check: Limited sharing options for results.
Validate with people who use this workflow before building.
Hypothesis 4
Add a favorites feature to quickly access commonly used names.
Assumption to check: No way to save favorite names or templates for repeated use.
Validate with people who use this workflow before building.
App evidence
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
App Store description
Have you ever needed to randomly pick names out of a hat and not have the necessary materials to do so? I've heard the scenario all too many times. You have the names, but what about a hat? There's not a fedora in sight. Your sleepless nights are about to end! Introducing the "Names in a Hat" application - just the tool you need to pick random names out of a hat. Features: * Save multiple lists of names and teams. * Tap to pull a name out of the hat. * Standard Draw - quickly draw a random order. * Team Draw - divide the names into teams. * Secret Santa - randomly assign people as gift givers and gift receivers. * Infinity Draw - continually draw from the same hat. * History - view your recent drawings. * Share your results in your favorite apps.
Written user reviews are not shown here. Check current App Store reviews >
Screenshots
< Scroll to see more >
Build scope
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Define the first version
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Set boundaries
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Check the hard parts
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
SUGGESTED BUILD STACK
React Native
Expo
@react-navigation/native
expo-clipboard
@react-native-async-storage/async-storage
react-native-share
BUILD KIT DIFFICULTY
Starter
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.
