Desktop
The desktop app runs alongside the game — iRacing, ACC, AMS2, rFactor 2, LMU, Rennsport, F1 — capturing as you drive, with live overlays and lightweight coaching prompts. It works offline: a lost network never loses a session.
The loop
Four steps — capture, brain, plan, improve — that turn every session you run into a concrete plan for the next one.
Step 01
Two surfaces, one canonical bundle. Every lap — at your rig, on your phone, or on a RaceBox clipped to the dash — finalises into the same schema before it ever reaches the backend.
The desktop app runs alongside the game — iRacing, ACC, AMS2, rFactor 2, LMU, Rennsport, F1 — capturing as you drive, with live overlays and lightweight coaching prompts. It works offline: a lost network never loses a session.
At a real track, pair a RaceBox and drop the phone on the dash. Sessions finalise safely even if the phone sleeps or the LTE drops mid-stint. The iPhone app ships first; Android follows with the V1 release.
Step 02
Weaknesses, prescriptions, and the sim↔real bridge — three things the server computes so the desktop and mobile apps stay thin.
Every session is scanned for patterns that recur — late braking into T1 at Spa, early throttle on exit at Silverstone. LAP groups them by car, track, and conditions, then stores each as a weakness with a severity score that moves as you practise.
Each open weakness pairs with a drill from a rule-based coaching library we curate by hand — a target metric, a target value, a session count. Every drill traces back to a specific rule; nothing is generated on the fly.
Paired sessions on the same track get compared by the server: the shape of your inputs (the lines in a brake trace, the curve of a throttle pickup) versus their intensity (peak pressures, slip angles, steering rates). Shape transfers across worlds; intensity is often calibrated to the wrong one.
Step 03
After the brain finishes analysing a session, it emits a plan — not a graph, not a long report, but a short list of drills you can execute in the next practice slot.
A plan never asks more of you than you can execute in a single practice slot. Three or four drills max, each sized to a handful of laps — not a quarter-hour video to watch before you drive.
Every drill ships with a number you can hit or miss — "trail-release to 12% at apex over three sessions," "minimum speed +1.5 km/h at T6 at Spa over five laps." Vague coaching ("brake later") is not a drill; a measurable number is.
Step 04
After you drive the planned session, LAP compares the new telemetry to the targets the plan set — and writes a verdict on every drill before your next practice slot opens.
The next session's numbers are compared to your own baseline — not a pro driver's, not a cohort average. Your baseline moves as you improve, so the target for the same weakness gets harder over time.
Every line of the plan gets one of three outcomes: closed, improving, or still open. No partial credit — either the number moved or it did not. Closed patterns give up their spot on the plan; open patterns get a revised drill next session.
Honest disclosure
We would rather under-promise than ship a claim we cannot back. Here is what you get when you start the trial this week — and here is what is on the roadmap but not yet in the product.
For interested developers
The standards we hold ourselves to and the public integration surface LAP reads from. Every link goes to a canonical reference — W3C, MDN, EU law, the sim publisher’s own page — so you can cross-check what this site says against the source.
10 / FINISH LINE · CHEQUERED FLAG
Fourteen days free. Then €15 a month, or €150 a year and save €30.
No card at signup · Cancel anytime