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.
Build your own keyboard!
$3.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 Keybuild: map the core Utilities 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: Users often find password management tedious and time-consuming.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Many users request better customization for password generation options.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Some users experience bugs with clipboard functionality.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Users want a more engaging user interface.
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.
Build your own keyboard! Touchscreen keyboards don't need to be one-size-fits-all, so let's change that! With Keybuild, you choose the layout, the keys, everything. Keys can be set up to type whatever you want! Letters, greek letters (ɑ, β, ɣ), maths symbols (π, ∫, ∑), arrows (↑→↓←), or even your favourite emoji can be added and organised depending on your needs. Create multiple ‘panes’, each containing keys arranged using a stack-based layout, and switch between them with either an automatic menu, or direct links. Add a small number row to your Qwerty keyboard, or have a try using Azerty or Colemak layouts. Build a keyboard that can keep up with your maths-heavy university course, or specialist profession. Or just make a dashboard for your favourite emoji. Or do all that and more, it's up to you! This app does its best to supports VoiceOver, and accessibility APIs. Technical note: This app is 99% SwiftUI, which is as close as you can get while we wait for the ‘SwiftUI Lifecycle’ to come to Custom Keyboard Extensions! SwiftUI powers this app's advanced functionality, as well as some of its more unusual bugs. :) Disclaimer: This iPad app is available on Apple Silicon Macs, but macOS currently does not support keyboard extensions. Still waiting for that tablet Mac!
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.