02 COMPLEX PRODUCT LIVE

LIVE — RUNNING, IN USE

ICS Playlist Studio, and the discipline of a read-only mode

Ten minutes before a class, an instructor is still assembling the set. Ninety seconds into it, they are riding it live, with a room watching. Generating a good playlist for indoor cycling turned out to be straightforward. Serving the same person in both of those states — authoring and operating — did not.

Ride Mode on a phone: the intro screen of a ride
Ride Mode on a phone: track 1 of 4 with cadence and cues

RIDE MODE ON A PHONE INTRO AND TRACK 1 / 4 THE REAL DEPLOYMENT, READ-ONLY

CONTEXT

Indoor Cycling Stuttgart runs strength rides: music mapped to a ride structure, with cadence, intensity blocks and leadership cues. Building one by hand is an hour of work.

The operating conditions are the real constraint. Instructors finish a set minutes before a class, in a studio, on a phone, with a room filling up. Then the class starts and the context inverts: they are no longer editing, they are executing, in front of twenty people, with no attention to spare.

A single interface that serves both states serves neither.

MY ROLE

Product design and build. Sole designer and engineer.

Responsible for the generation model, the studio interface, the Ride Mode split, and the deployment.

INTERACTION MODEL

01 HUMAN

02 HANDOFF

03 AGENT

Stays the author.

Two seams, not one.

Proposes structure, keeps time, commits nothing.

—

Sets the ride intent: type, structure, duration, the cues that make it theirs.

—

Edits every generated block. The draft is a starting point, not a verdict.

—

Decides when the set is finished and the ride begins.

—

Generation → authoring: the system returns a complete but fully editable draft. It never publishes on its own.

—

Authoring → Ride Mode: crossing this seam is a deliberate act, and it removes every editing capability.

—

Ride Mode offers no way to modify or delete.

—

Maps ride structure to track selection and block timing.

—

Produces a coherent whole rather than a list of suggestions.

—

Holds the beat for the whole ride, so the room stays in time and the instructor calls it instead of counting it.

—

Can change nothing during a ride. Keeping time is the only authority it has there.

AUTHORITY MODEL

Two modes, and what each one puts within reach.

An instructor has two jobs that never happen at the same time: building a session, and running it in front of a room. So the app has two modes, and they don’t have the same powers.

CAPABILITY

AUTHORING

RIDE

VIEW

✓

Available

✓

Available

NAVIGATE

✓

Available

✓

Available

MODIFY

✓

Available

—

not offered

DELETE

✓

Available

—

not offered

What the authoring mode and Ride Mode each put within reach

A confirmation dialog still allows an unsafe action. It just adds a step in front of it. In Ride Mode, editing isn’t hidden behind a warning — the mode doesn’t put it in reach at all.

The system can suggest changes to a session. Nothing goes in until the instructor accepts it.

IN THE STUDIO

Ride Mode, read-only on purpose.

Ride Mode on the phone, the way instructors use it during a class. Shown as images only, the app itself stays with the studio.

Ride Mode on a phone: the intro screen of a ride
Ride Mode on a phone: track 1 of 4 with cadence and cues

DECISIONS

Ride Mode is strictly read-only. No edit, no save, no delete — the mode doesn’t put them in reach.

BECAUSE

During a class, an accidental touch isn’t a minor annoyance — it’s a visible failure in front of a room of people who paid to be there, at the one moment the instructor can’t look down and recover.

WHAT IT COSTS

An instructor who notices a mistake mid-ride genuinely cannot fix it in place. They have to leave Ride Mode to do it.

Accept that cost rather than softening the boundary.

BECAUSE

Leaving a mode is a conscious act; a mis-swipe is not.

WHAT IT COSTS

The recovery path is slower than it could be, and that is the point.

WHAT COULD GO WRONG

Mid-ride, under load, the instructor taps the wrong thing and changes the session.

AUTHORITY

GUARDRAIL

Changing a session is an authoring decision, never a ride decision.

Ride Mode doesn’t put modify or delete in reach.

RESULT

IN USE

STATUS

Prep collapsed to seconds

Live

Playlist, movements and live delivery in one — each track cued about five seconds before it plays, at the same quality every ride.

The screens above show the real deployment, in read-only Ride Mode.

REACH ME

Say hi.

Next.js, TypeScript, Tailwind. Statically rendered, no backend. Set in IBM Plex Sans and IBM Plex Mono. Built and audited against WCAG 2.2 AA.

vincent & blendwick ART DIRECTION & PRODUCT DESIGN STUTTGART

IMPRINT PRIVACY

02 COMPLEX PRODUCT LIVE

LIVE — RUNNING, IN USE

ICS Playlist Studio, and the discipline of a read-only mode

Ten minutes before a class, an instructor is still assembling the set. Ninety seconds into it, they are riding it live, with a room watching. Generating a good playlist for indoor cycling turned out to be straightforward. Serving the same person in both of those states — authoring and operating — did not.

Ride Mode on a phone: the intro screen of a ride
Ride Mode on a phone: track 1 of 4 with cadence and cues

RIDE MODE ON A PHONE INTRO AND TRACK 1 / 4 THE REAL DEPLOYMENT, READ-ONLY

CONTEXT

Indoor Cycling Stuttgart runs strength rides: music mapped to a ride structure, with cadence, intensity blocks and leadership cues. Building one by hand is an hour of work.

The operating conditions are the real constraint. Instructors finish a set minutes before a class, in a studio, on a phone, with a room filling up. Then the class starts and the context inverts: they are no longer editing, they are executing, in front of twenty people, with no attention to spare.

A single interface that serves both states serves neither.

MY ROLE

Product design and build. Sole designer and engineer.

Responsible for the generation model, the studio interface, the Ride Mode split, and the deployment.

INTERACTION MODEL

01 HUMAN

Stays the author.

—

Sets the ride intent: type, structure, duration, the cues that make it theirs.

—

Edits every generated block. The draft is a starting point, not a verdict.

—

Decides when the set is finished and the ride begins.

02 HANDOFF

Two seams, not one.

—

Generation → authoring: the system returns a complete but fully editable draft. It never publishes on its own.

—

Authoring → Ride Mode: crossing this seam is a deliberate act, and it removes every editing capability.

—

Ride Mode offers no way to modify or delete.

03 AGENT

Proposes structure, keeps time, commits nothing.

—

Maps ride structure to track selection and block timing.

—

Produces a coherent whole rather than a list of suggestions.

—

Holds the beat for the whole ride, so the room stays in time and the instructor calls it instead of counting it.

—

Can change nothing during a ride. Keeping time is the only authority it has there.

AUTHORITY MODEL

Two modes, and what each one puts within reach.

An instructor has two jobs that never happen at the same time: building a session, and running it in front of a room. So the app has two modes, and they don’t have the same powers.

VIEW

AUTHORING

✓

Available

RIDE

✓

Available

NAVIGATE

AUTHORING

✓

Available

RIDE

✓

Available

MODIFY

AUTHORING

✓

Available

RIDE

—

not offered

DELETE

AUTHORING

✓

Available

RIDE

—

not offered

What the authoring mode and Ride Mode each put within reach

A confirmation dialog still allows an unsafe action. It just adds a step in front of it. In Ride Mode, editing isn’t hidden behind a warning — the mode doesn’t put it in reach at all.

The system can suggest changes to a session. Nothing goes in until the instructor accepts it.

IN THE STUDIO

Ride Mode, read-only on purpose.

Ride Mode on the phone, the way instructors use it during a class. Shown as images only, the app itself stays with the studio.

Ride Mode on a phone: the intro screen of a ride

DECISIONS

Ride Mode is strictly read-only. No edit, no save, no delete — the mode doesn’t put them in reach.

BECAUSE

During a class, an accidental touch isn’t a minor annoyance — it’s a visible failure in front of a room of people who paid to be there, at the one moment the instructor can’t look down and recover.

WHAT IT COSTS

An instructor who notices a mistake mid-ride genuinely cannot fix it in place. They have to leave Ride Mode to do it.

Accept that cost rather than softening the boundary.

BECAUSE

Leaving a mode is a conscious act; a mis-swipe is not.

WHAT IT COSTS

The recovery path is slower than it could be, and that is the point.

WHAT COULD GO WRONG

Mid-ride, under load, the instructor taps the wrong thing and changes the session.

AUTHORITY

Changing a session is an authoring decision, never a ride decision.

GUARDRAIL

Ride Mode doesn’t put modify or delete in reach.

RESULT

IN USE

Prep collapsed to seconds

Playlist, movements and live delivery in one — each track cued about five seconds before it plays, at the same quality every ride.

STATUS

Live

The screens above show the real deployment, in read-only Ride Mode.

REACH ME

Say hi.

Next.js, TypeScript, Tailwind. Statically rendered, no backend. Set in IBM Plex Sans and IBM Plex Mono. Built and audited against WCAG 2.2 AA.

vincent & blendwick ART DIRECTION & PRODUCT DESIGN STUTTGART

IMPRINT PRIVACY