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.
This is the makeover of the original iGeocacher app I wrote back in 2008
$1.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.
Rork plan preview for iGeocacher: map the core Navigation 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 user engagement features
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: No offline functionality
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Poor discoverability of geocaches
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No user feedback mechanism
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.
This is the makeover of the original iGeocacher app I wrote back in 2008. I believe it was one of the first if not the first apps for the serious geocacher. I've wanted to do this since the original 32bit app was no longer supported but never had the time it seemed. The advent of AI coding assistance in Xcode allowed me to do a complete makeover in a fraction of the time. It has some features that I haven't seen in any other geocaching apps, most notably the SONAR ranging simulation that I had in the first app. It is extremely helpful when chasing down geocaches in the wood where the footing is tricky. The auto ranging allows you to "home in" without having to focus on the compass display. The app parses standard .GPX files known as "pocket queries" from the geocaching website and displays them in easy to use lists and map views for selection and targeting. The navigation display, patterned after the directional gyro display in light aircraft, show a simultaneous view of your current heading and bearing to the selected cache target while displaying the distance to the target. Turn on the SONAR feature and the app provides a simulated SONAR ping and echo sound effect that simulates the SONAR pings and echoes you've heard on all those submarine movies. That's really handy when riding a bike or driving a car toward a cache because you get an audio indication of target proximity.
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.