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 last night of the charter, six people, one purse of shared money for expenses, and nobody is sure who owes what.
$6.99
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.
Loading build analysis and prompts…
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.
The last night of the charter, six people, one purse of shared money for expenses, and nobody is sure who owes what. Rainbow's End Ship's Purse is the bookkeeper's ledger for a shared kitty. Everyone pays into the purse, the purse pays the running costs, and at the end each person gets one figure: what they hand the purse, or what the purse hands them. WHY IT'S DIFFERENT — Nobody settles with anybody but the purse. Whoever paid in less than their share owes the purse. Whoever paid in more, or paid for the boat out of pocket, is owed the difference. What is left goes back in proportion to each share. The crew sees the same ledger on their own phones with the free Ship's Purse Guest. THE BUDGET — A worksheet sized from the voyage: breakfasts, lunches and dinners aboard, meals ashore, fuel by the hour meter, moorings, dockage, water and ice, fees, the crew tip, and a contingency. You set every rate; the app never guesses a price. The total sets the opening round per share. SHARES — Everyone starts at a full share. A child at half board is 0.5. A guest aboard four days of seven is 0.57. Someone who joins mid-cruise owes only the rounds from then on. THE LEDGER — Money paid in by cash, Venmo, Zelle or card, several people at once around the table. Expenses paid from the purse or by a guest. A guest who paid for the boat is reimbursed in cash or credited against the next round. A top-up round when the purse runs low. A mistake is struck through with a reason, never erased. An expense can carry a photo of its receipt. THE CASH — Cash is kept apart from money sent electronically, so you can count it and see whether it is short or over. The count is recorded; nothing is adjusted on its own. ON ONE SCREEN — Spending by category against the budget, what is left in the purse, and who still owes on the latest round. MID-CRUISE — Change the budget and the difference becomes a round for everyone, up or down. SETTLE — One line per person. Refunds come from the cash first. Mark each one paid as it happens. SHARE WITH THE CREW — Switch on sharing and the app shows an eight-character code. Anyone with Ship's Purse Guest types it and reads the purse: the ledger, the receipts, and their own share due and balance. The purse is sealed with a key made from the code, and we never see the code or read the purse. Treat the code like a key: give it only to your crew, and tap New code when the crew changes. A change goes up from any screen, and the purse screen says when the crew last received it. WITH LOGBOOK — Send an expense and its receipt photo to Rainbow's End Logbook, or to another phone by AirDrop. An expense sent from Logbook waits on the purse screen until you link it to an existing line or add a new one. Nothing is added until you tap. EXPORT — A PDF statement, a spreadsheet for the books, and a backup, through the share sheet. A worked sample, a week in the Exumas with seven people and one who joined late, shows every screen before you enter anything. On iPhone and iPad. Works offline. No account, no subscription, no server of ours. Your entries stay on your phone and leave it only when you share the purse, send an expense, or export it. The method comes from Charles Parette, who kept charter kitties by hand and in spreadsheets for years. We built it aboard our ketch Rainbow, for the charters where the whole crew keeps one purse. WHAT IT WON'T DO • Move money. Payments happen in cash or your own apps; the purse records them. • Split one bill among part of the crew. Every expense is shared by everyone's share. • Keep more than one currency in a purse. • Let the crew enter anything. The bookkeeper writes; the crew reads. • Cover the charter fee or the airfare. It keeps the costs of the cruise itself. Ship's Purse is an aid to keeping the kitty, not a substitute for counting the cash. May you find a rainbow's end and treasure found wherever you sail or set your anchor. Apps for sailors, by sailors.
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.
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.