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.
Explore an unfamiliar city, wander through narrow streets—and suddenly you no longer know where your cruise ship is docked, where the bus is waiting, or where your hotel is
$2.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.
Queued for a daily kit update.
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 Navigate Back: map the core Travel 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.
Explore an unfamiliar city, wander through narrow streets—and suddenly you no longer know where your cruise ship is docked, where the bus is waiting, or where your hotel is. Navigate Back was created for exactly these situations. SAVE PLACES AND PLAN TRIPS Save hotels, berths, meeting points, destinations, or the location of your car. Add an address, GPS coordinates, notes, and important contacts. Prepare your trips at home on your iPhone or iPad. THREE WAYS TO EXPLORE Map Navigation: Choose a saved place, an address, or GPS coordinates. Navigate Back provides turn-by-turn directions—on foot, by bicycle, by car, or by public transport. Your journey is recorded along the way, and the outbound and return trips can be saved as separate tracks. Compass Navigation: When there is no suitable road network, the app shows the direct direction to your destination, along with the distance, estimated arrival time, and other information. Ideal for trips away from marked paths, across open terrain, or on the water. Your actual path is recorded automatically and saved as a separate route. Free Movement: No destination and no directional guidance—simply start walking, running, or riding. Navigate Back automatically records your path. Ideal for bike rides, hikes, walks, and exploratory trips where the journey itself matters. PHOTOS, MARKERS, AND TRIP DETAILS Add markers along the way and link photos to your route. After your trip, view details such as distance, duration, pace, elevation profile, steps, and more. You can also use your recorded track to help retrace your journey. STAY ORIENTED OFFLINE Using GPS and the compass, you can determine your current position, direction, and distance to your destination—even without a cellular connection. The app transfers all relevant destination data directly to Apple Maps for navigation. If the required maps have been downloaded in advance, navigation is also available offline. CONTACTS AND TRANSLATION ASSISTANCE Save phone numbers for tour guides, bus drivers, the ship’s reception desk, or family members. The conversation feature translates spoken or typed text and can read the translation aloud. Navigate Back is not an emergency, rescue, or maritime navigation service. In immediate danger, contact the local emergency services. When on the water, always use the required navigation equipment. COMPANION APP FOR APPLE WATCH On Apple Watch, you can view previously saved destinations and routes, use the compass to check direction and distance, and call important contacts. You can also start navigation on the paired iPhone. New places, contacts, and routes must be created in the iPhone or iPad app. The Watch app does not provide independent route planning or turn-by-turn navigation and requires a compatible iPhone with Navigate Back installed. PRIVACY No account, no registration, and no advertising or cross-app tracking. Location and route data are used only for features you initiate and are stored locally. When synchronization is enabled, the data is synced between your devices through your personal iCloud account. Navigate Back gives you the freedom to explore—and helps you find your way back later. Learn more about the story behind the app and all its features: https://www.onetwoapps.com/en/navigateBack.html
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: Lack of user reviews limits trust in the app
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited features compared to similar apps
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Navigation can be confusing at times
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No offline capability for maps
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.
Not assessed in a Build Kit yet.
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.