Unfortunately, they don’t have anything as lightweight, elegant and usable as James’ application. If you load the page
above on a mobile device it makes 66 different network requests, transferring a staggering 1.1MB of data.

Really, TFL?

Seriously, if anyone from TFL ever reads this, please, please, please go take a long look at the GDS Digital Service Standard
and then go and fix your shit.

I really miss bus.abscond.org, so I decided to fork James’ TFL Live Bus code, and see if I could get it to work with the new API.

Here is the equivalent page to the TFL one I showed earlier. Currently, it makes 5 network requests, and transfers
11KB of data to provide the relevant information.

As you might imagine, it loads faster, too - especially on a mobile device (which is the most important kind, for this sort of service).

Best of all, you get a bookmarkable URL for every stop. I tend to use the same few stops every week,
going to and from work, so that was an essential feature of bus.abscond.org which I really miss when trying to use the TFL service -
you can get bookmarkable pages out of it, but they certainly don’t make it easy.

I hope people find this useful, at least until TFL make me shut it down.