00Project

Revvy Studio

The pit wall for the driver’s team — the car live, a coach afterwards, and the progress across drives

Year
2026
Platform
Web app · iPad and iPhone
Modes
Racing · Rally
Status
Final UI (V3.1) · in build
01Context

What is Revvy Studio

Revvy Studio is the team’s side of Revvy: a web app for the friend on the pit wall, served by the racing PC — scan a code and it opens, no download. Live follows the car during the drive, Coach replays and explains it afterwards, History turns the evening into progress. Studio follows the game: racing or rally, the same screens fill with the right content.

  1. LiveDuring the drive

    Where the car is, how it is, and what the driver and Revvy are saying — no video.

    • L1WaitingRally: At the start line
    • L2Drive
    • L3Car
    • L4TimingRally: Splits
    • L5Talk
    • L6Alert
    • L7Finished
  2. CoachAfter the drive

    Revvy’s review: the best lap, the moments that cost time as real frames, and what to try next.

    • C1Review
    • C2Moment
    • C3Incident
    • C4LapsRally: Runs
  3. HistoryAcross drives

    Every drive of the evening — all, racing or rally — and what keeps coming back.

    • H1Drives
    • H2Progress
02Ecosystem

The other half of Revvy.

The driver talks to the in-car Revvy; the team works in Studio. The two sides are always connected: the car’s data flows to Studio, the team’s radio flows back to the driver — the team never controls the driver’s Revvy.

  1. The driver’s side

    In-car Revvy

    The visor HUD and Revvy’s voice, in the helmet — for Racing and for Rally.

    Built
  2. The team’s side

    Revvy Studio

    The car live, the team radio and a coach after every drive, on a tablet or phone.

    Final UI · in build

Car data flows to the teamThe team radio flows back to the driver, timed by the in-car Revvy

Who does what

Facts for Revvy, calls for the team

01
Revvy
The facts and the timing: numbers, brake calls, pace notes, safety and technique. The team never has to read numbers out.
02
Team
The decisions — box, push or bring it home — and the human side: calming, encouraging, what Revvy can’t see.
03
Driver
Confirms with one word, and Revvy acts. Without Studio, Revvy makes every call on its own.
03User journey

One session, end to end.

A session is two people in one room — the driver in the rig and a friend on the pit wall — with Revvy between them. The journey follows all three from gearing up to the next goal; the lowest point is the incident, and that is where Revvy checks in first.

User journey

One session, three points of view

A driver in the headset, Revvy in the car and a friend on Studio, from gearing up to the next goal. Racing and rally share this journey; rally swaps laps for runs, and the pace notes own the stage.

BeforeDuringAfter
01Gear up02HUD setup03Scan and connect04Team mode on05Drive06Ask Revvy07Revvy suggests08Team calls it09Incident10Finished11Review12Progress13Next goal
DriverIn the headsetPuts on the headsetPicks two side slotsPre-race HUD setup—“Team is on the radio.”Pushes for a lap time“How are my tyres?”—Hears “Box this lap.”, says “Box”Spins off · stopsSees resultsBest lap firstListens to Revvy’s reviewSees the trendPicks 1–2 focuses
RevvyIn the car—Saves the slots per driver—Switches to team modeDecisions go to the teamBrake cues · pace notesAnswers + tyre panelIn a side slot, then backSuggests “Box this lap?”To Studio, with the reasonPlays radio on a straight“Are you OK?”12 s silence → marshalsBuilds the reviewMarks the momentsReads the reviewStops at each momentCompares like with likeSame track · same routeCoaches them next run
TeamStudio · iPad / iPhone——Scans the QRStudio opens · no downloadTurns on team modeRadio opensWatches Live · DriveSees the question in TalkReads the suggestionDecision · 10 sHolds to talkQueued → On air → DeliveredAlert takeoverUrgent talks nowFinished · Open CoachReview → MomentHistory · Racing / RallyShown on the next L1“Next time · from Revvy”
FeelingHow it feels, step by step
Lowest point → Revvy checks in; help is one word awayGoes home with a plan
Driver actsRevvy actsTeam actsSafety firstA decisionDriverTeamScroll sideways
Flow map

Every screen, and how you get there

Live, Coach and History are one tap away from anywhere — the iPad’s top bar, the phone’s floating bar. Under each screen, where the eye goes first. Racing and rally share this map: Timing becomes Splits, and Laps becomes Runs.

Liveduring the driveCoachafter the driveHistoryevery driveLive tabs · Drive · Car · Timing (Splits) · TalkL1Waitinghub status · last driveL2Drivegap to bestL3Cartyres + GL4Timinglap tableL5TalkRevvy, nowL7FinishedOpen CoachL6Alertwhat happenedC4Lapsreplay + traceC1Reviewone-line verdictC2Momenttwo real framesC3Incidentlast 3 secondsH1Drivesbest drive · All / Racing / RallyH2Progressthe trendleaves pitschequered flagserious alert · any tabcar moves onOpen CoachOpen Coach · last driveLapsmomentnextdrive cardOpen T4 in CoachProgress

Live · Coach · History one tap from anywherePlay review walks C1 → C2 → C3 in orderReview chip (phone: back row) returns to C1Coach context menu → drive pickerHistory filter: All · Racing · Rally · Progress dims AllRally: Timing → Splits · Laps → Runs · same positionsL6 takes over any Live tab; Urgent talks now

Main pathBack or shortcut
Key flows

Four moments, three points of view

Flow 1 · Connect and team mode

A friend joins from the sofa — no app, no account.

Studio opens from a QR on the PC. The radio stays off until team mode is on; then Revvy hands decisions to the team.

DriverIn the headset
RevvyIn the car
TeamStudio · iPad / iPhone
Scans the QR on the PCDesktop join screen
Studio opensNo download · paired
Waiting for the driverL1 · hub · game · driver
Turns on team modeRadio opens
Opens the secure linkOnly while team mode is on
Tells the driver
“Team is on the radio.”
Hold to talk is readyReady · team radio on

Before team mode: Hold to talk and Urgent are disabled; Mark worksEvery request through the tunnel needs pairingTeam mode off → Revvy makes the calls again

Flow 2 · Who decides to box

Revvy suggests, the team decides, the driver confirms.

Revvy owns facts and timing; the team owns decisions. The radio moves through its states: Holding → Sending → Queued → On air → Delivered.

DriverIn the headset
RevvyIn the car
TeamStudio · iPad / iPhone
Front left heating up
Asks “Should I box?”
“Asking the team.”Sends it to Studio
Sees “Revvy suggests”With the reason
Box this lap?10 s · no answer → Revvy answers
Keeps watching
Holds to talkHolding → Sending
QueuedWaits for a straight
Plays it on a straightOn air
Hears “Box this lap.”
Says “Box”
BOX card on the HUD
Guides into the pits
Sees “Delivered”Box confirmed

Decision questions go to the team; safety calls still go straight to the driverNo answer in 10 s → “No word from the team. My call: …”

Flow 3 · Off track, car stopped

Safety first, then back to the start.

Revvy checks on the driver at once. The team sees the alert take over and can talk now, without waiting for a straight. The moment is marked for Coach.

DriverIn the headset
RevvyIn the car
TeamStudio · iPad / iPhone
Spins off · stops
“Contact. Are you OK?”
Alert takeover12 s timer · Urgent talks now
Driver answers?
“I’m OK.”
Rejoins carefully
“Help is on the way.”Help · or 12 s silence
Marshals arrive
Back to the startRace grid · rally start line
Marks it for CoachAuto Mark
Sees “Back at start”
Incident in CoachC3 · why it happened

Never says “simulated”Marshals stay 8 s while the car stands, then a black cut back to the start

Flow 4 · After the drive

From the chequered flag to the next goal.

Live ends on Finished, Revvy builds the review, Coach walks through it, History shows the trend — and the next session opens with the focus.

DriverIn the headset
RevvyIn the car
TeamStudio · iPad / iPhone
Takes the flag
L7 · FinishedRevvy is reviewing it
Builds the reviewMarks moments · checks numbers
Opens CoachC1 · Review
Plays Revvy’s review2 min · stops at each moment
Reads it aloud
Moment · IncidentC2 · C3 · you vs reference
Laps · RunsC4 · any lap vs best
HistoryAll · Racing · Rally
Next timeOn the next L1
Picks 1–2 focuses

Every number comes from telemetry; Revvy explains itRally compares only runs on the same routeProgress dims All: laps and stage times do not compare

04During

Watch the car, hear the conversation.

During the drive, Live shows where the car is, how it is, and what the driver and Revvy are saying — without video: the footage waits for Coach. Each screen leads with one thing to read first, and racing and rally share every position.

The screens

Seven, one focus each

Live, waiting for the driver: hub connected, game not running, driver not on track; the last drive on the paper tile, 1:33.108, and three things to try next timeLive at the start line: hub, game and driver all green; the last run on Centre, 4:40.9, and three things for the next run
  1. 1Status“Waiting for the driver.” Hub, game and driver light up in turn; Live opens by itself when the car leaves the pits.
  2. 2Last driveThe last drive on the paper tile: best lap 1:33.108, 2 incidents, 4 timed laps — and Open Coach at its foot.
  3. 3Next timeThree things to try, from Revvy’s last review.
  4. 4Car and RevvyThe car, and whether Revvy coaches and the team is on the radio.
  5. 5Team modeTeam mode, on every Live screen. Off, Revvy makes every call and the radio stays closed; on, decisions go to the team and the radio opens — Revvy tells the driver “Team is on the radio.”
iPad · Racing · L1 Waiting
On a phone

The same screens, one column

On a phone

The pit wall in one hand

Live · Coach · History float at the bottom; the screen’s tabs sit under the lap.

  1. 1Lap, team mode and tabsLap 3 of 4 and the Team mode switch; then Drive, Car (with an alert dot), Timing, Talk.
  2. 2Gap and lapThe paper tile with the gap; the lap, the best and the speed beside it.
  3. 3Next turn and map“T8 · brake in 92 m”, then the track, its sectors coloured against the best.
  4. 4AlertsThe two that matter now.
  5. 5Talk rowHold to talk, Urgent and Mark, above the mode bar.
  6. 6TyresThe four tyres on the chassis; the hot rears in orange.
  7. 7Revvy’s read“Rears are hot: right 139° all lap, left 111° and rising.”
  8. 8G-forceThe disc and the reading: 2.1 g, braking into T8.
  9. 9SystemsBrakes, engine and fuel.
05Radio

One voice at a time.

Revvy, the team and the driver share one channel: the driver’s ear. The team talks with one button; Revvy picks the moment — on a circuit by priority, on a rally stage after the pace notes.

Team mode

The team turns the radio on

One switch on every Live tab, racing and rally. Off, Revvy decides and the radio stays closed; on, decisions go to the team and the radio opens. Turning it on asks once; turning it off is instant — held messages are cancelled, and Revvy tells the driver “Team is off the radio. I’ll make the calls.”

Figma · State · Team mode
The talk row

Ten states, buttons that never move

Figma · State · Team radio
01
Push to talk only
The mic is open only while Hold to talk is held; release sends. Before team mode is on, the buttons rest and Mark still works.
02
One status line
Ready → Holding → Sending → Queued → On air → Delivered, said in one line above the buttons; Failed and Expired are the exits.
03
Rally: same buttons
On a stage Urgent waits for the current pace note, normal radio is held to the finish — and held messages never expire.
Who speaks first

Six levels

A higher level waits for nobody below it; the driver’s own voice is never cut, except by danger.

  1. 1Danger“Contact.” · Team UrgentCuts in at once
  2. 2Timing“Brake now.” · pace notesAlways on time
  3. 3Driver’s question“Fronts 92, rears 88.”First sentence first
  4. 4Team radio“Box this lap.”Waits for a straight · rally: held to the finish
  5. 5Revvy notices“Tyres need attention.”Waits · may drop
  6. 6Coaching“Look through the apex.”Gives way first

Driver talking → everyone waits, except dangerOne voice at a time; Revvy yields at once

Rally

The notes own the stage

On a stage the co-driver’s voice comes first. Normal team radio is held to the finish; Urgent is for safety and plays after the current note; a stopped car opens the radio at once.

  1. Start lineRadio open
    • “Dry to the forest, wet after 5 km.”
    • Proposes a caution · water 5.0 km
    • Driver accepts · Revvy adds it to the notes
  2. On stageHeld to finish
    • Revvy reads every pace note
    • Hold to talk → held to the finish
    • Urgent → after this note: “Stop, car off at 5.2!”
  3. Car stoppedTalk now
    • “Are you OK?” · OK or SOS
    • Team talks right away · no waiting
    • No answer in 12 s → marshals
  4. FinishHeld messages play
    • “Stage complete. 4:40.9.”
    • Held messages play in order
    • Driver replies · radio open again
  5. Between stagesRadio open
    • Splits · damage check · tyre plan
    • Revvy suggests to the team: save the fronts
    • Driver asks the team anything

Notes own the stageNormal radio waits for the finishUrgent is for safety onlyCar stopped → talk nowTeam proposes notes · driver accepts

06After

Every lap, replayed and explained.

After the drive, Coach opens on Revvy’s review: the best lap, where the time went, and the moments that matter, as real frames from the recording. Play the review and Revvy talks it through in about two minutes, one moment after another.

Coach Review, racing: “L3 was your best lap. L4 was quicker but left the track at T8.”, most to gain T4 · 2.4 s, the lap pills, Play review, the moments as real frames, and next timeCoach Review, rally: “One run of 4:40.9 with 3 incidents: too fast into pace-noted corners.”, most to fix the left five, the split pills, Play review, the three incidents and next time
  1. 1The storyOne sentence first — “L3 was your best lap. L4 was quicker but left the track at T8.” — then the most to gain, incidents and laps.
  2. 2Paper tileThe best lap on paper, with the clean average under it.
  3. 3Laps · SplitsEvery lap as a tile, the full width: L3 purple for the best, L4 orange for the off. Tap one to open it in Laps.
  4. 4Play · AskPlay review: Revvy talks through the race in about two minutes. Or ask Revvy anything about it.
  5. 5MomentsThe moments, most time first, as real frames from the recording — the off framed in orange.
  6. 6Next timeThree things to try next time.
iPad · Racing · C1 Review
On a phone

The review, then each moment

On a phone

Coach in one column

  1. 1Race and tabsRace 22:19 · 911 GT3 RS — Review and Laps.
  2. 2Story and best lapOne sentence, then the best lap on paper.
  3. 3Most to gainT4 · 2.4 s — and Play review · 2 min.
  4. 4MomentsReal frames, most time first; the off in orange.
  5. 5MomentBack to Review · T4 · 1 of 6.
  6. 6Two clipsL2 (you) above L3 (the best), from the same metre.
  7. 7What happened“156 at the slowest point. L3 carried 200 here.” — and the numbers.
  8. 8ControlsPrevious, pause, next — and the next thing to try.
07Across drives

Every drive, and what keeps coming back.

History lists every drive of the evening — all of them, the races or the rally runs — and turns them into progress: the best lap of each race, or the speed before each incident on a stage, and the one pattern worth working on next.

History Drives, All: “Four drives this evening. Your best lap came in the 22:19 race.” — a rally run and three races, newest first, each with a real frameHistory Drives, Racing: three races with their best laps, the best 1:31.523 in purple, and an empty card to race againHistory Drives, Rally: one run on Centre, 4:40.9 with 3 incidents, a card to run Centre again, and the stage itself: 7.83 km, 3 splits, 68 pace notes
  1. 1SummaryOne sentence for the evening: “Four drives this evening. Your best lap came in the 22:19 race.”
  2. 2DrivesEvery drive, newest first, with a real frame from it — rally and races together, the best in purple.
  3. 3FilterAll · Racing · Rally: All lists every drive by time.
iPad · History · H1 Drives · All
On a phone

Drives and progress

On a phone

History in one column

  1. 1Filter and tabsAll · Racing · Rally, then Drives and Progress.
  2. 2Summary“Three races. Best lap in the 22:19 race.”
  3. 3DrivesA real frame from each race and its best lap; an empty card for the next.
  4. 4Totals3 races, the best lap 1:31.5, 3 incidents.
  5. 5Headline“Found 1.05 s, then lost 1.59 s.”
  6. 6ProgressThe gap to your best, race by race.
  7. 7Comes backT4, in every race: 3 / 3.
  8. 8FocusOpen T4 in Coach, at the foot.
08Design evolution

Six designs, three rounds.

Studio’s UI began as a wireframe that held everything, then went through three directions, two refinements and one final combination, built as a system. The same two screens, Live and Coach, show every step.

The wireframe

Everything on one screen

The first Studio grew out of the ecosystem blueprint. A first draft had sixteen sections, including community and training; it was cut to two jobs — watching the car live and looking back afterwards. The wireframe that followed was complete: every panel a team could want, racing and rally mirrored one to one, iPad and iPhone, with Coach and History added later. As a map of the content it worked; as a screen it was too busy.

Wireframe · Live
Wireframe · Coach
The brief

Edit down to the bare minimum

01
No grey cards
Grey card backgrounds read as generic. Groups come from space and hairlines instead.
02
One focus per screen
Navigation splits the content into instruments and clusters, so the eye knows where to look first.
03
Big numbers, little text
Large numbers and simple instruments; small text only where it earns its place.
04
Tyres that read as tyres
At first glance — and a simpler, moving shape for G-force.
05
Real frames
Replays show frames from the recorded drive, never drawn sketches.
06
For hobbyists
Enough for small teams and amateur racers, in a calm, comfortable layout.
Three rounds

Six designs

Each direction was drawn in full — every screen of Live, Coach and History, on iPad and iPhone, with a flow map — before choosing. Round one tried three languages; two went on, with Space Grotesk and more information back; round three combined them.

Start
Round 1
Round 2
Round 3 · Final
V3.1: Live Drive on an iPad
Round 3 · A’s look, C’s order

V3.1

A’s dark, professional look with C’s way of organising — one paper-white tile per screen for the number to read first — built on auto layout, tokens and components, Racing and Rally on the same skeleton.

  • Dark track base, one paper-white tile per screen
  • Bars to compare; orange only for act or hot
  • Spacing on one scale, 4 to 48; eleven type roles
  • 54 screens: Racing, Rally and All, iPad and iPhone
Final UI · in build
Why V3.1

A’s look, C’s order

Round 2 · A

Why A looks professional

  • Black, hairlines and light numerals — like race dashboards and timing screens, calm at night and in the pits
  • Bars and tables: lengths compare, numbers line up
  • Front-view tyre blocks: race tyres at a glance
  • Disciplined colour: orange to act, purple best, green faster

Every number about as loud as the next: the eye scans the whole layout before it knows where to look.

Round 2 · C

Why C reads at a glance

  • One solid focal shape per screen holds the key number
  • Shapes group the information: a label and its value together
  • States as shapes and icons — filled now, hollow next, a tick for done
  • A sentence first, then the data

Light paper doesn’t suit the track or the night; circles can’t compare sizes, and times get cramped inside them.

Round 3

V3.1: the rules

  1. 1Dark track baseFrom A: black, hairlines, light numerals; small caps only for section labels.
  2. 2One paper-white tileFrom C: the black circle becomes a white tile on dark, holding only the number that matters most.
  3. 3Bars to compareSplits, inputs, you against the best; circles stay for laps, steps, buttons and the G disc.
  4. 4Orange means actHold to talk, alerts, hot tyres. Purple is the best, green is faster — and a sentence before the data.
09Design system

Built as a system.

V3.1 keeps V3’s layout as it was and rebuilds it as a system: every group an auto-layout frame, every gap on one spacing scale, eleven type roles, components for everything that repeats — and Racing and Rally on the same skeleton.

  • Auto-layout frames01,028
  • Loose layers on screens1,6040
  • Font sizes4111 roles
  • Text using a style0%99%
  • Spacing bound to tokens01,516
  • Components022 + 25 icons

Measured on the 52 V3.1 screens (26 Racing, 26 Rally) against the 26 V3 screens, 12 Oct. Every gap and padding (1,516) is bound to a space token; the 1% of text without a style is the logo. Data graphics are drawn inside fixed frames and are not counted as loose layers.

Tokens

Colour, type and space

A dark track base where orange is the only loud colour and always means act, hot or incident. Numbers are Light, words Regular, buttons and chips Medium — all Space Grotesk. Every gap is a step of one scale.

  • bg / canvas#000000The screen
  • text / primary#FFFFFFMain text, white tyres
  • text / secondary#8C8C8CLabels and meta
  • text / tertiary#4A4A4ADecoration only, never text
  • line / tile#2E2E2ETile outline, 1.5 px
  • accent / act#FF6A1FAct now · hot · incident
  • accent / go#3DDC84Faster than the reference
  • accent / best#B48CFFBest lap · best run
  • accent / slower#FFC23DSlower than the reference · track maps only
  • paper / bg#F4F3EFThe hero tile, one per screen
  • 4
  • 8
  • 12
  • 16
  • 20
  • 24
  • 32
  • 40
  • 48
RoleiPadiPhoneUse
Display12072Light · The one hero number or alert
Big8848Light · Second number: lap clock, speed
Number5632Light · Values in tiles
Title4024Regular · Sentence headlines
Quote2818Regular · What was said, insights, steps
Heading2217Regular · Item titles, times in lists
Body1715Regular · Running text
Button1715Medium · Buttons, the active tab
Label1513Regular · Tile labels, meta
Small1412Medium · Chips, badges
Caps1212Medium · Section labels — the floor
  • HeroPaper fill — one per screen
  • Tile1.5 px outline — secondary groups only
  • AlertOrange fill — takeovers
Components

17 sets, 5 components, 25 icons

Figma · Components · V3.1
Racing ⇄ Rally

Same skeleton, six slots

Studio follows the game’s mode, so switching never moves a control: no screen changes its grid, about 80% of the modules are shared, and rally swaps the content of six slots — the next pace note instead of the gap, splits instead of timing, runs instead of laps.

RacingRace 22:19 · 911 GT3 RSRallyRun 1 · Pine Ridge · Centre
Drive · paper tileRacingGap to the best lap · −1.48 · sector barsRallyThe next pace note · L6 left six, slight · in 71 m · split bars
Drive · clockRacingLap 3 of 4 · best, last, idealRallyRun 1 · 5.36 of 7.83 km · last and next split
Drive · mapRacingA closed track, its turns, the carRallyA point-to-point stage: start, splits, finish, incidents
Third tabRacingTiming — laps and sectorsRallySplits — split points and segments
Talk · radioRacingPlays on the next straight, at most 8 sRallyHeld to the finish; Urgent for safety only
AlertRacingOff track → the rescue stepsRallyContact → damage check, the driver kept going
Coach · referenceRacingThe best lap’s frame at the same metreRallyThe pace note that was called — a first run has no best
History · progressRacingBest lap per race, as a gap to the bestRallyTop speed before each incident; runs compare on the same route
Every size

Three classes, one logic

01
Compact · under 600 px
Phone screens: one column, the header on top, the body scrolls, a floating Live · Coach · History bar.
02
Medium · 600–1099 px
The iPad top bar; rows of three blocks become two, the last one wraps to full width.
03
Expanded · 1100 px and up
The iPad screens as drawn at 1376; above 1680 px the content stays 1680 wide and centres.
Motion

Calm, quick, nothing bounces

01
One easing family
A standard, an enter and an exit curve. The pill or underline slides to the new tab in 180 ms; content cross-fades, never slides.
02
Live data stays still
Digits change instantly, no counting up; bars and gauges ease over 200 ms with each 4 Hz sample.
03
Alerts arrive, then leave
A takeover rises 24 px and fades in over 400 ms, and fades out when the car moves on. Reduced motion turns every move into a fade.