How it's built
The interesting part isn't the display. It's the data.
01
Schedule + live delay join
TransLink retired their old stop-estimates API. The current feed only gives delays per trip, so we built the join against the static GTFS schedule ourselves.
02
Quota-safe caching
TransLink's API caps out at 1,000 requests a day. A backend polls once and caches it, so any number of screens can read from one shared fetch.
03
Runs in any browser
No app, no install. The display is a static page that polls the backend and refreshes on its own.
04
Where it stands now
Built and tested against real TransLink data. A deployable product for real installs is next.