Mobile
LAP for mobile.
The desktop client captures your sim sessions; the mobile app captures the real-world half of your driving. Same driver profile, same prescriptions, both halves of the cross-platform promise.
Real-world capture
From the track day to your driver profile.
Track-day data is what tells you whether the trail-braking habit you fixed on sim is actually showing up at the real-world circuit. The mobile app captures it. Phone GPS is the entry-level path — open the app, start the session, drive. No extra hardware, no export step. The session syncs to your driver profile the next time you have signal, so a weakness flagged on Saturday becomes a sim drill the same week.
For high-fidelity data, a bluetooth GNSS receiver (RaceBox or compatible) raises the sample rate enough to support sector deltas at the same resolution the sim side gives you. The integration detail lives in the next section.
RaceBox integration
High-fidelity data without pro-grade gear.
Phone GPS samples at roughly 1Hz — fine for lap times and broad-stroke trends, not enough to call out where you lose four tenths in turn three. A bluetooth GNSS receiver fixes that. RaceBox samples at 25Hz, the same threshold the data-logger appendices in your race series specify; it is the unit most track-day drivers reach for when they want sector-level resolution without the cost of a dedicated motorsport datalogger.
Pairing is a one-time bluetooth handshake from the LAP mobile app. After that the receiver is automatic — turn it on at the track, the app picks it up, the higher sample rate takes over for the session. Compatible bluetooth GNSS receivers from other vendors work with the same code path; RaceBox is the one we have validated end-to-end.
Wear OS companion
Glance at your wrist between sessions.
A small companion app for Wear OS smartwatches. At a track day the phone usually lives in a pocket; the watch is what you can actually look at between sessions without breaking your prep. Glance at your last lap time, the gap to your reference lap, and which weakness you flagged for the next stint.
The Wear OS companion ships with the V1 release after public beta, not at beta itself. The phone app is the headline experience; the watch is the convenience layer that comes once we have the phone surface dialled in.
Android
Android first, iOS later.
The mobile app launches on Android at public beta. It works on any modern Android phone with bluetooth — the capture path itself is light, and a track-day phone usually has plenty of unused horsepower while it sits in your pocket between sessions.
iOS support is on the roadmap and lands with the V1 release, not at public beta. If you race exclusively on an iPhone today, the waitlist is the right place to wait — we will email you when the iOS app ships, not before.