Mac · iPad · iPhone
A control pad for your Mac, on an iPhone or an iPad. Lay out a deck on the Mac — buttons, toggles, sliders, knobs, a piano, the apps that are open — and it is on the pad a moment later. A press opens an app, sends a key chord, runs a command, moves the volume or plays a note. No hardware to buy. That is CTRLpad.
· Not released yet — for the Mac, the iPad and the iPhone


Every picture on this page is CTRLpad itself: the designer on a Mac, and the pad in Apple's iPad and iPhone simulators, paired to it, on the decks File ▸ New Deck makes — Desk, Stream and the MIDI controller.
The song is invented: Night Shift by The Quiet Testers, put in the Mac's Now Playing with no sound behind it. The apps along the foot are the ones that were open on that Mac; CTRLpad keeps that row itself.
The deck
A deck is tabs, and a tab is a grid. Drag a control where it goes, give it an action, and every paired pad has it a moment later. Close the designer and the pads keep working: CTRLpad lives in the menu bar.
Undo Resize Volume. What is in the way moves aside, a full tab grows a row to take what is added, and a move with no room says why.
Thirteen kinds of control
Twenty-six kinds of action
iPhone & iPad
A tab is laid out in landscape. Held upright, the grid turns with the phone, so every control keeps its neighbours and nothing shrinks to a sliver.

A group is a row, a column or a grid of buttons: your own, and after them the ones the Mac makes and keeps current. Put one on a tab, or dock it at an edge, where it stays whichever tab is up.
A MIDI controller
Everything comes out of the Mac's virtual MIDI
source, CTRLpad, which any app that takes MIDI sees as a device: no driver,
no cable. File ▸ New Deck ▸ MIDI controller is what a controller on a desk has, on three
tabs.


The Mac itself, on the pad
Two controls that are the Mac's own, live. Both run only while a pad, or the designer's Play, shows them.
A screen control shows the Mac's main display, the pointer on it, at the size that pad draws it — encoded in hardware for each pad, on a connection of its own so a press never waits behind a frame, and only when something on the screen changed.
A Touch Bar control shows the bar of the app in front — its own buttons, sliders and scrubbers, and the Control Strip — as the Mac draws it, and a finger on it is a finger on the bar. Bring another app forward and its bar comes up.
Measured
A press is thirty bytes on a stream with no delay. It is decoded, carried out and answered on the connection's own thread, never waiting for the window. Sliders send one value a display frame.
Round trips measured with the pad in Apple's simulator on the same Mac; a real network adds its own.
In a terminal
The model, the layout and the wire are a Rust
library, and ctrlpad is a command line in front of it — pairing with a Mac
and pressing its controls like a pad, from a script.
ctrlpad hostsThe Macs on the networkctrlpad pair <host>Pair with the six digits, oncectrlpad press <host> <id>One input, and the ran line back with the Mac's millisecondsctrlpad show --hostThe deck, with the Mac's own buttons and their keysctrlpad new --preset midiA ready-made deck: starter, apps, touchbar, screen, midictrlpad check · layoutEvery rule a deck breaks; where its controls land on a screenPrivacy, itemised
The specific version, phrased so that you could go and verify it. The formal version is dopecode's privacy policy.
/usr/bin/perl with a small library of its own loaded
into it — only while a tab shows a now-playing control and a pad or Play can see it.The honest part
Better read here than found out afterwards.
Accessibility and Screen Recording are given in System Settings, by you, and no installer can give them. macOS hands Screen Recording only to an app started after it is turned on, so CTRLpad offers to reopen itself.
The Mac app cannot be on the Mac App Store: it posts keystrokes, runs shell commands and is not sandboxed. The Touch Bar and what is playing come from parts of macOS Apple does not document, and an update to macOS can change them.
Help
Open CTRLpad on the Mac, then on the iPhone or iPad, and pick the Mac from the list. Type the six digits the designer's sidebar shows, under Pairing. That is once: from then on the pad finds the Mac and connects by itself.
On the same network, or near each other: with no network at all they reach each other peer to peer. Not over the internet. Both ask once whether CTRLpad may use the local network; it needs that answered yes.
The Mac has not given CTRLpad a permission that control needs, and the sentence with it says which: Accessibility for key chords, Escape, typed text and a screen's mouse; Screen Recording for a screen. Both are in System Settings ▸ Privacy & Security.
macOS gives it only to an app started after it was turned on. The designer's sidebar offers Reopen CTRLpad; the pads reconnect by themselves.
Choose CTRLpad as a MIDI input in the app's MIDI settings — it is there as soon as CTRLpad runs. Map a knob by the app's own MIDI learn: turn it on the pad.
Yes, each paired once. Each shows the tab it is on, and each has a MIDI channel of its own, so two pads are two controllers.
On the Mac, in ~/Library/Application Support/CTRLpad/deck.json, with a
copy of the deck as each day began, the last fourteen: File ▸ Restore from
Backup brings one back. Export and Import move a deck between Macs,
pictures and all.
Still stuck? Write to hello@dopecode.com with your CTRLpad version and what it said.
Mac · iPad · iPhone · not released yet
CTRLpad is not released. Write to us and we will tell you when it is — the Mac app, and the pad for the iPhone and the iPad.
· Questions first? Help answers the common ones.