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 morning of October 6, 1981, began like any other: waking up from a restless sleep, preparing for the day ahead of you and driving to the ranger station where you've worked for the past 11 years
$3.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 Aurora Hills: Chapter 2: 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 puzzle variety can lead to repetitive gameplay.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: In-app purchase prompts may disrupt gameplay.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Difficulty levels may not suit all players.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Lack of social features for sharing progress.
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 morning of October 6, 1981, began like any other: waking up from a restless sleep, preparing for the day ahead of you and driving to the ranger station where you've worked for the past 11 years. Aurora Hills was once a tranquil community nestled within the mountains of Appalachia, but a series of disappearances have all but shattered the serene atmosphere. Only a feeling of desolation permeates the surrounding as you drive through the now dilapidated small town. Jen wasn't at the ranger station when you arrived that morning. Being the only other park ranger, she likes to get an early start to the day and by the time you arrived, she had driven to one of the many closed off hiking trails to start searching for the missing people. Following her trail of notes, you make your way off the main trail to meet up with her to explore the remote parts of the national park. When you find her camp however, your worst fears are realized: The site's been ransacked, her equipment strewn across the campsite, her tent's been torn up, and Jen is nowhere to be seen. There's no time to turn back now, it's already midday and the sun sets early this time of year. The only thing worse than wandering into the forest alone is braving it at night. You can't abandon Jen now, not when the trail is so fresh. Now you have no choice but to venture deeper into the uncharted parts of the national park, the parts mythologized into local urban legends by frightened townsfolk. You'd better leave soon, you may never get a better chance to uncover the dark history of Aurora Hills... Developed by the creators of Meridian 157, Aurora Hills: Chapter 2 is the second part in a series of point and click puzzle adventure games. Based in the year 1981 in a small West Virginian community, Aurora Hills follows the journey of Ethan Hill, a park ranger tasked with investigating strange disappearances from the region. Explore the rolling hills of West Virginia, find clues of the whereabouts of the missing people and solve intriguing puzzles to solve the mystery of Aurora Hills! Features: • Custom soundtrack and sound effects designed for a creepy in-game atmosphere • Challenging and clever puzzles • A logical hint system for some of the most difficult riddles • Available in 9 languages, including English, French, Russian, German, Chinese (Simplified), Spanish, Portuguese, Italian and Japanese! • New colour blind mode available for people who might have trouble with colour based puzzles • Has a hard mode, for those who want to enjoy even more challenging puzzles! Follow us to receive all the latest news! Facebook: https://www.facebook.com/NovaSoftInteractive/ Twitter: https://twitter.com/novasoftint Instagram: https://www.instagram.com/novasoftint/ YouTube: https://www.youtube.com/c/NovaSoftInteractive
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.