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.
Mononoke is an unconventional synthesizer, designed to compose evolving soundscapes and musical textures
$8.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 Mononoke: map the core Music 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: Difficulty finding specific tracks or playlists
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited offline playback options
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of social sharing features
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: User interface can feel cluttered
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.
Mononoke is an unconventional synthesizer, designed to compose evolving soundscapes and musical textures. Feedback routing What sets Mononoke apart from other synths is that its voices (4 in each section) can be routed back into each other in multiple ways, creating all sorts of overtones and pulsating resonant frequencies. Sometimes harmonic, sometimes weirdly atonal. Sometimes clear and delicate as icicles, sometimes harsh as metallic blades, sometimes soft as fresh snow. This interaction between voices helps fuse all layers together into a coherent musical landscape. A tale of two engines The synthesizer engines (each of the two sections has its own independent engine) have relatively simple controls, which influence a complex system of many invisible, interconnected LFOs. But this is not your bread-and-butter general purpose synthesizer: think of Mononoke as one huge FM synthesizer where each voice is an independently playable operator. Together all operators contribute to a single soundscape. Expressive pads Complex soundscapes can be created live, using the 8 performance pads which let you modulate each voice independently in several dimensions. Your interactions with the pads will also be sent out as MPE/MIDI (when loaded as an AU plugin in a compatible host) so you can record and tweak your session. The onscreen pads can be latched individually so some voices can be used as drones, while others as can be added and removed as extra sonic layers. The pads are fully integrated in the Audio Unit plugin. Connectivity Mononoke is designed as an AUv3 plugin, with advanced Audio Unit features such as MPE input and output (!), a fully exposed array of AU parameters for automation and all the connectivity and scalability you can expect from modern plugins. The standalone mode is basic (just meant for jamming and creating presets) and does not offer any connectivity, so if you want to use Mononoke in conjunction with other apps and effects you'll need to load it into a host, such as Garageband, Audiobus, AUM or Cubasis. Summary: - Audio Unit (AUv3) plugin - 8 voice polyphony, 2 independent engines with 4 voices each - Compatible with MPE (MIDI Polyphonic Expression) and MIDI - MIDI Input and Output (only available when used as an Audio Unit plugin) - Limited standalone mode for jamming (full screen, no connectivity) - 8 independently tunable performance pads for expressive interaction - Universal, fully scalable to any screen size, supports fullscreen mode in AU hosts - Freely tunable voices, or quantized to semitones (with overall finetuning) - iOS10 (MIDI/MPE output from the plugin requires iOS11) or higher Also contains Mononoke Pads: an extra AUv3 MIDI controller plugin for playing MPE compatible synths using Mononoke's pads. Note: this is a separate plugin which will be installed in your MIDI Plugin collection. Mononoke Pads requires iOS 11.
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.