Every part of Gridshift follows from one goal: less time between an idea and hearing it. Knowing how that goal shapes the app makes the rest easier to guess.
One window, the song keeps playing
You choose a sound while the song plays, change it while it plays, and hear each choice in context. Editors open in place instead of in windows of their own. See How Gridshift Thinks.
The keyboard reaches everything
Nearly every command has a name in the Command Palette (⌘K), and most have a key. The mouse works everywhere too; both ways are described on every page. See Keyboard and Mouse. Copies are one click or one key away too: Stamping.
The palette matters as much as the canvas
A painter’s palette decides what ends up on the canvas. In music, that palette is your samples, patterns and presets. Most DAWs treat it as folders on a disk and leave the sorting to you. Gridshift ships no sounds of its own (free ones to start with) and builds your palette in: the library is part of the app, so finding and trying a sound is part of making the track, not a detour.
Tidying is not making music
Sorting samples is the classic way to avoid finishing a track. Gridshift does as much of it as it can on its own, and leaves the rest for moments you would not make music anyway, such as on the train with the iPhone app. At the desk you make music.
A second opinion away from the desk
A track sounds different on headphones, in the car and on a phone speaker. The iPhone app plays every saved version, so you hear where the track stands and note what works and what does not.
Who it suits
Gridshift fits producers who build tracks from sounds they collect (samples, loops, patterns and presets) and who like to stay on the keyboard. It fits less well if you perform live by launching clips, want a large set of built-in synths and effects, or record and comp long live takes.
Next: Why a Built-in Library explains the palette. Last modified on October 23, 2026
