Platform
Live departures and disruption alerts for a regional rail network.
- Client
- Northline Transit
- Role
- Frontend lead
- Year
- 2025
- Duration
- 9 months

Results
- Weekly riders
- 84k
- six months after launch
- Store rating
- 4.7
- both stores
- Crash-free sessions
- 99.8%
The challenge
Riders checked three places before a trip: the timetable PDF, a social feed for delays and the station screens. None of them agreed for long.
The network's feed updates every fifteen seconds, and most riders open the app on a platform with one bar of signal.
The approach
We designed for the worst platform first: the last good answer stays on screen with its age, and new data slides in without moving what you're reading.
Alerts are per journey, not per line, so a rider hears about the 8:12 they take, not every train on the route.
What I built
- Departure boards that work offline and say how old they are.
- Journey alerts with a quiet-hours schedule.
- Screen reader support tested with riders who use it daily.
Ada argued for the rider on the platform with one bar of signal in every meeting. That rider is why our reviews changed.

