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.
Develop a feel for "real" Japanese through onomatopoeia.
$5.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 1000 Japanese Onomatopoeia: map the core Reference 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 content variety in reference apps
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Lack of engaging UX/UI
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Difficulty in searching or filtering content
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No offline access to content
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.
Develop a feel for "real" Japanese through onomatopoeia. To any student of Japanese, the staggering number of onomatopoeia seems daunting. What on earth, for instance, is the difference between からから, かりかり and くりくり? They may sound similar, but each carries a wealth of information modulated by emphasis, context and grammatical function. Thus からから can be used to describe someone laughing loudly, a vehicle rattling along, being parched with thirst, or being out of money; かりかり something crispy, or someone irritable; and くりくり something round/chubby and lovable. In Japan, onomatopoeia are a natural and familiar vernacular in tune with all walks of life. Hip youths in Roppongi bars speak in a language peppered with onomatopoeia derived from Japan’s rich pop culture of manga and anime. At the same time, within university walls, erudite academics sprinkle their lectures with onomatopoeia, and even the most respected newspapers will employ them to describe economic conditions, be they sluggish (のろのろ) or booming (ぐんぐん). Onomatopoeia are used everywhere, and this is why it's so important for learners to become familiar with them as early as possible. Along with Japanese idioms and proverbs, onomatopoeia are a rich and fascinating aspect of the language that is obscured in many textbooks, yet used on a daily basis in all areas of Japanese life and culture. This is the first comprehensive dictionary of Japanese onomatopoeia. Multiple English sample sentences highlight every meaning and nuance of expressions, and furigana (as well as audio) allows even beginners to correctly pronounce and use the phrases immediately. Other app features include: - Incremental search in English and Japanese - Spell-checking in English and romaji - Bookmark, annotate and share entries - Jump to other apps and web dictionaries - Portrait + landscape modes - Slide Over Multitasking Mode (iPad) - Split View (iPad, Plus/Max phones) - Night mode (dark mode) - Share Extension to add cards to Anki - Widget Based on “1000 Japanese Onomatopoeia” by William de Lange, TOYO PRess.
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.