Case study ·

2025

Kite Maps

A route planner that keeps the map at 60 fps while recalculating. Routing runs in a worker and the line redraws as you drag.

Role

Route planner

Client

Kite Mobility

Stack

MapLibre · Svelte · Web Workers

Result

Frame drops 18% → 0.4%

Kite Maps route planner: map with a bike route, route card with 14 minutes and phone navigation screen

01 — The problem

The map froze when it mattered.

Kite’s route planner froze for half a second every time a route was recalculated, which is exactly when people drag the map to look around.

Desktop · 1440 px

Kite map comparing three bike routes, quiet, fastest and scenic, with a traffic stress chart

01 —

The quiet way

Three routes, one calm choice

Three routes, one calm choice

02 — What I built

Routing moved off the main thread.

Routing moved into a Web Worker, the map stayed on the main thread, and the route line is redrawn progressively while the worker answers. Every drag state was designed and tested on a mid-range Android phone.

Phone · 390 px

Three Kite phone screens: choosing a city offline, downloading the map, and riding through a dead zone

02 —

No signal, no problem

Download once, ride offline

Download once, ride offline

Component · 4 states

The Kite turn banner in four states, plus watch and lock screen versions

03 —

Readable at arm's length

Turn banner, four states

Turn banner, four states

03 — What changed

The most used screen in the app.

Dropped frames during recalculation went from 18% to 0.4%. The planner is now the most used screen in the app.

0.4%

dropped frames while a route recalculates, from 18%

#1

most used screen in the app

Create a free website with Framer, the website builder loved by startups, designers and agencies.