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.
Two lines of trigonometry, in the runup area, with the ATIS still in your head
$4.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.
Your first Build Kit is free with a verified email.
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.
Two lines of trigonometry, in the runup area, with the ATIS still in your head. Crosscheck does them and draws the answer. Type the runway and the wind. You get the crosswind and the head or tailwind, and — the part that matters — the runway drawn with the wind across it at the real angle, so which side it is on is unmistakable. Knowing the number is easy. Picturing the side wrong under pressure is what puts an aeroplane in the grass. THE GUST IS THE NUMBER THAT DECIDES Plan on the steady wind and land in the gust and you planned the wrong number. The headline figure is the gust; the steady one is underneath it, because you brief both. IT WORKS THE OTHER END WITHOUT BEING ASKED Every wind is computed for the reciprocal too. If that end is the better one — a headwind instead of a tailwind, or materially less across — the app says so with the numbers already on it, and swaps with one tap. That is the question you actually have when a crosswind is marginal, and no other calculator answers it. GRADED AGAINST YOUR FIGURE, NOT OURS You type the demonstrated crosswind from your own POH. The app compares your number to the computed component and tells you where you sit — within it, close to it, or past it — and it names which figure it means, the crosswind or the tailwind. There is no built-in aircraft database, on purpose. Demonstrated crosswind varies by model, by year and sometimes by modification, and a figure that is close but wrong is worse than no figure at all. For most light aircraft the demonstrated crosswind is a DEMONSTRATED value — the strongest crosswind a test pilot happened to find during certification — not a structural or regulatory limit. Some types are placarded with a real limit. The app says so where you enter it. DENSITY ALTITUDE TOO Field elevation, altimeter setting and OAT give you pressure altitude and density altitude, using the standard approximation printed in POH supplements. AND THE CLOCK RULE, HONESTLY The mental shortcut you were taught — angle off over sixty, times the wind — shown against the real figure at every angle, so you can see exactly where it starts over-reading. At 60° it says the full wind when the answer is 87%. WHAT IT IS NOT A planning aid, not an authority, and not a source of weather. It has no network connection of any kind: it does not fetch METARs, and the wind it uses is the wind you typed. Verify against the current ATIS or ASOS. It does not compute weight and balance, takeoff or landing distance, or performance of any kind. The pilot in command decides. Works offline. No account.
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.
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.