# Build a music playground

Build a native Tauri application for making rhythms and melodies by playing with patterns. Build it extremely well for musical experimentation. Follow the [shared launch](../shared/launch.md), honoring an explicit preference for another framework.

The person should be able to make something they like before they know much music theory. Start with a good-sounding example they can take apart, some useful instruments, and a clear way to hear the consequences of a change.

## Make sound easy to explore

Let the person place drum hits and notes into repeating patterns, start playback, and change the pattern while listening. They can alter the tempo, choose instruments, and adjust the balance between parts. Make it easy to add a sound, remove it, or try a different one.

Show where playback is in the pattern so the person can connect what they see with what they hear. Give timing enough care that a steady rhythm stays steady during editing. A click, a dragged note, or an instrument change should produce an understandable result.

Choose controls that invite experimentation. The person may prefer placing notes on a grid, playing them on a keyboard, or another approach suited to the idea you develop together. Give them a complete, enjoyable way to compose with both rhythm and pitch. Helpful musical defaults can make the first attempts sound good while leaving room to try something stranger.

## Develop an idea

Once the person likes a pattern, let them save it, duplicate it, and make a variation. They might remove the drums for an opening, bring them back for the next section, and finish with a different melody. Provide an understandable way to arrange those ideas into a longer piece.

Make it clear whether an edit changes a reusable pattern or just one part of the arrangement. Preserve previous work through useful undo and saved versions. Someone experimenting with the melody should feel free to discover that the earlier version was better.

Include enough control over individual parts to understand why the whole piece sounds different. Muting a part, hearing it on its own, and adjusting its level should help the person listen and decide. Let the appearance of the application fit the kind of music toy they want to use.

## Keep what they make

Save the editable project with the notes, instruments, patterns, arrangement, and other choices needed to reopen it accurately. Export playable audio that the person can hear outside the app and share with friends. Help them choose where the exported piece begins and ends, including an appropriate ending for sounds that continue after the last note.

Keep the app useful with its delivered instruments and sounds. Explain any additional downloads or services when the person chooses to add them. Apply the shared launch's ownership and recovery guidance to the projects they create.

## Listen to the result

Deliver the installed application and make a short piece together. Start from the example, change its rhythm and melody, make a variation, and export the arrangement. Reopen the saved project and listen to the exported file in an ordinary player.

Judge whether the controls help the person hear and pursue their own ideas. Use the experience to teach the relationship between a sound, a pattern, an arrangement, and the finished recording. Their requests can begin with what they hear: “Bring that in later,” “Make this part softer,” or “Let me try a different sound.”

Later projects can add recording, new instruments, or phone-based performance controls. Preserve existing projects so the person can use new sounds and controls in music they have already made.