Patrn
Patrn connects a court’s multi-camera setup to the player’s phone. I designed the mobile and club-side flows that take a session from QR scan to published highlight.

A recording app only feels simple when it hides the hard parts.
Challenge
Starting a recording depended on a QR code, the player’s location, an available court, several cameras, and enough storage. After the match, the footage still had to be processed before anyone could edit or share it.
Approach
I designed the flow around the moments a player actually sees: join the court, start the session, wait for footage, choose a clip, and post it. Technical states are explained only when they affect the next action.
Start from the court, not a settings screen
Scanning the court code identifies the location and session. The player confirms what the system already knows instead of configuring cameras before a match.

Show what is happening after the final point
Processing can take time, so the library shows which matches are still being prepared and which clips are ready. The wait becomes a visible state rather than a dead end.

Keep editing deliberately small
Players are trimming a point, not producing a film. The editor keeps the clip in focus and limits controls to the few decisions needed before sharing.

End with a pattern players already know
Caption, tagged players, and club location sit in a familiar post composer. By this stage, the camera system has disappeared from the experience entirely.

“Players came to play padel, not operate a camera system.”
Core design principle