Generative features
Plan a generative beatbox
A worked example of building, connecting and distributing a drum instrument with optional generation.
Imagine a beatbox with playable pads and an option to ask for a new kick, snare or texture. This example describes a product you could develop with Maru. It is not an announcement of a finished template or a complete automatic workflow.
Start with the playable instrument
Choose a small set of sounds and map them to pads. Make the levels and controls useful before adding online features. Save the bank and instrument configuration so the existing kit has a clear playback path.
Build an instrument or effect explains the project choices. A sampler bank may be enough for a prepared kit; a custom module can add product-specific behavior.
Connect the player's account
Register a creator app and arrange generation access for your module. The player signs in with their Maru account and approves the app's generation permission.
Explain that the new-sound action uses their credits. The creator's product price and the player's generation spending are separate unless an explicitly agreed offer says otherwise.
Generate, choose and keep a take
The player asks for a short wooden hit. The product shows the job's progress while the existing kit remains usable. In a website module with connected generation, a completed take is saved to their library for import.
If you want “replace this pad” to happen inside the beatbox, your host must implement loading the selected sound and preserving it with saved state. The generation action alone does not do that. Generation in your products compares the options.
Distribute the right version
A website version needs a host that offers connected generation. You can also distribute the selected sounds in a prepared bank or an available native plugin release. Native plugins do not yet offer the same in-interface generation flow as website hosts.
Plan licensing, included content, updates and the behavior when signed out. Licenses and product access separates activation from account consent.
Understand the business
A player who generates a sound has not necessarily bought the beatbox. Use sales reports to review purchases, activation records to review product access and usage reports to review generation, as explained in creator reporting.
Selling on Maru describes the marketplace direction and beta onboarding. Contact us with your target host, example kit and who should pay for generation to discuss automatic pad loading, integration access or a commercial pilot.