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.
At our boutique NGO (Asociația unPi pentru Școlari, www.unpi.ro/english) we stive to build assistive solutions for all humans.
$0.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 Lidar Eyes: 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 reviews and feedback on app performance.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Potential issues with lidar tech integration in diverse environments.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Monetization may not be clear with only a $0.99 initial charge.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Competition with established navigation apps.
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.
At our boutique NGO (Asociația unPi pentru Școlari, www.unpi.ro/english) we stive to build assistive solutions for all humans. This application is the very first step in designing a helpful guide for the visually impaired. Here we are using the latest hardware (LiDAR) and latest software APIs (Spatial Audio) from Apple in order to create a virtual guide, which would try to emulate a human friend of the visually impaired. Imagine that you are travelling together with your best friend and he or she is informing you about your surroundings, plus alerting you on the nearest obstacle in your path. Our solution requires a LiDAR sensor in your iPhone (iPhone 12/13/14 Pro), and for best sound experience: an AirPods Pro/Max in transparency mode. While our efforts are ongoing, we rely and ask your support plus feedback in building additional features (i.e. Computer Vision for iPhone without LiDAR) for this application or the upcoming ones. To free your hands, this application requires you to wear your iPhone on a chest mount holder, plus wear headsets with support for spatial audio and transparency so that you remain aware of your environment at all times. If you don’t have a chest mount holder, try to point the iPhone’s Lidar (back cameras) towards the path you’re heading when using the app Once you start Lidar Eyes Lite, you'll be able to hear a sound coming from the direction where the closest obstacle is located. For a better experience we recommend to download and select an enhanced or premium voice from Settings > Accessibility > VoiceOver > Speech > Voice for your system’s language. For now, the application announcements are available in the following languages: - English - French - Italian - Romanian - German - Spanish - Chinese, Simplified
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.