Benchmark candidate map libraries on this device (open it in the Tesla browser). Each run scripts an identical ~45s drive — pan, zoom, rotate, pitch, fling — and measures FPS + frame stability, then emails a report to support@codriver.io.
How it works. Each engine page auto-runs the same scripted camera timeline and reports six headline numbers (avg FPS, p95 frame time, jank %, worst frame, load latency, frames). The full suite chains all pages and, after the last engine, emails a single recap with every engine side by side (ranked by FPS) for easy comparison. Running a single engine on its own still emails just that one report. Every run is under a minute.
Strategy spread. WebGL vector (MapLibre, Mapbox, Google-vector), Canvas/DOM raster (Leaflet, Pigeon), Canvas raster + rotation (OpenLayers), GPU raster (deck.gl), Canvas2D vector (protomaps-leaflet). The point is to see which rendering strategy stays fluid on the weakest hardware.
Email delivery: checking…. Tokens for Mapbox / Google are optional (?mapboxToken= / ?googleMapsKey=).