Per-app trackpad scenes.
A scene is a trackpad layout bound to an app. The idea is simple; the details decide whether it feels natural or fights the app in front of you.
A per-app trackpad scene is a layout that changes when the frontmost app changes. In Safari, the trackpad might show back, forward, new tab, and a media scrub. In Figma, the same surface might show brightness, a screenshot corner, and undo/redo areas. In Terminal, it might show almost nothing. The point is not more gestures. The point is fewer mode switches.
Most trackpad utilities start with a global layout: one set of gestures for every app. That works until two apps want the same gesture, or until a gesture that is useful in a browser becomes dangerous in a terminal. Scenes solve that by making context part of the design.
Why global layouts break
A global layout assumes every app wants the same controls. They do not. A browser wants navigation. An editor wants windows and screenshots. A terminal wants restraint. A video editor wants transport and a way back to Mission Control. If the layout never changes, you either build a lowest-common-denominator surface or a surface that is wrong in half your apps.
The second problem is conflict. Two apps can claim the same gesture, or an app can claim a gesture the utility also wants. Scenes reduce the overlap by giving each app its own map.
How a scene works
The mechanics are similar across apps, even when the names differ:
- Detect the frontmost app. The utility watches the active app and selects the matching scene.
- Apply the layout. Edges, corners, areas, and the center gesture come from that scene.
- Fall back when there is no match. A default scene covers apps you have not configured.
- Yield when the app needs the input. Secure input fields, games, and remote desktops can suppress or capture the gesture layer.
The fallback is the part people forget. If every app needs a scene before the trackpad works, the system is too heavy. Start with a good default, then add scenes only where the default is wrong.
Scenes that work
| App | Useful scene | Why |
|---|---|---|
| Safari | Back, forward, new tab; brightness and volume on the edges | Navigation and media without leaving the page |
| Figma | Brightness, screenshot, undo/redo areas, Mission Control | Color checks, reference capture, and window switching |
| Final Cut Pro | Mission Control, screenshot, brightness, media scrub | Context switching around the timeline, not timeline editing |
| VS Code | Mission Control, screenshot, undo/redo, command palette | Keeps the keyboard primary |
| Terminal | Mission Control, screenshot, window halves | Restraint; destructive actions stay on the keyboard |
| Finder | New tab, back, forward, window halves | File navigation without a mouse reach |
How to design a scene
Three rules keep a scene usable:
- Three regions, not thirteen. One continuous control, one action, one escape hatch is enough for most apps.
- Do not duplicate a shortcut you already type faster. If you use
Cmd+Swithout thinking, a trackpad save button is noise. - Put destructive actions behind a deliberate gesture. A single edge tap should never delete, close, or send.
Then test for conflicts. Open the app, use the scene for a day, and remove anything you did not touch. A scene that looks clever in the editor and stays unused is not a scene; it is decoration.
When scenes do not work
Scenes are not universal. Games and remote desktops often capture input directly. Secure password fields can suppress event monitoring. Some apps already have deep gesture languages, and adding another layer creates double actions. In those cases, disable the scene or use a global fallback that stays out of the way.
Scenes also do not replace scripting. If a workflow needs a sequence of app commands, a conditional, or an API call, use a scripting tool. A scene is a layout, not a program.
Which apps support scenes
TrackStudio, BetterTouchTool, Multitouch, Curflow, and GestureCraft all support some form of per-app behavior. The differences are in the editing model: a visual surface, a trigger list, a drawn gesture, or a rule set. macOS built-in gestures do not have per-app layouts. The comparison in the 2026 roundup names where each one wins.
We make TrackStudio, so read that with the usual disclosure. TrackStudio’s scene model is visual: each app gets a layout, and a default scene covers the rest. It is $5 one-time (₹499 in India), with a 3-day trial, macOS 13+.
Frequently asked questions
What is a per-app trackpad scene?
A saved trackpad layout that switches when the frontmost app changes. It can change edges, corners, custom areas, and center gestures for each app.
Do scenes slow down the trackpad?
No, if the utility is well built. App detection is a lightweight system event. The noticeable delay comes from a badly designed scene, not the switch itself.
Can I use scenes with a Magic Trackpad?
Support depends on the app. Check the vendor’s documentation for your trackpad model and for external displays.
Do scenes replace BetterTouchTool?
No. BetterTouchTool is deeper for scripting and arbitrary automation. A scene is a layout; BTT is a platform. They can coexist if each gesture has one owner.