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.
Merge & Renovate at Hotel Legacy!
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 Hotel Legacy: Merge Game: 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.
Merge & Renovate at Hotel Legacy! Alyssa suddenly inherited a mysterious legacy from her grandmother—a Hotel Manor! She teams up with some interesting friends and desires to build her Hotel Empire! Join us as we merge and discover how she achieves her goals! Merge Fancy Items Serve guests with cozy service, fine cuisines, amazing drinks, and colorful souvenirs. The more you play, the more items you will be able to create! Let's merge together and become top-class hotel managers! Renovate Theme Hotels Buy new land, renovate old buildings, and turn them into wonderful hotels. Experience a totally different hotel style all over the world and throughout the ages! Build Relationships Meet guests from around the world. Listen to their stories and exchange fun life experiences. Guess who might find their true love during the journey? This game includes optional in-game purchases, including random-item purchases / loot boxes. There are hidden surprises waiting for you to discover! Join us on the journey of expanding Hotel Empires!
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 item variety leads to repetitive gameplay.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: In-app purchases can disrupt gameplay flow.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Difficulty in merging items can frustrate users.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Ads can be intrusive.
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.
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.