Dude, this is fantastic. Thank you. This is my biggest annoyance because I don't have reception in the elevator and I always only remember to check the bikes when I'm there.

For the SF Bay Area, the relevant endpoints are:

https://gbfs.lyft.com/gbfs/2.3/bay/en/station_information.js...

and

https://gbfs.lyft.com/gbfs/2.3/bay/en/station_status.json

With this I can build myself a little display that does the same. It does seem to match with the app, but in a tragic twist of fate it appears that the station closest to me has been delisted on the app. Oh fate! What the right hand giveth, the left hand takes!

EDIT: Funny that these days no one puts their RSS feed link somewhere visible. Fortunately, most clients do find it on the page quite easily. I wonder how they do. It's not in the HTML source.

▲

rahimnathwani 9 days ago | parent [-]

Here's a list, but it won't work in the elevator: https://tools.encona.com/lyftbike

▲

arjie 9 days ago | parent | next [-]

Haha, thank you. The app works quite well to see. I just want it to be available before I remember to ask, which I think I can create with an always on display.

▲

jeffbee 4 days ago | parent | prev [-]

That's pretty slick! But isn't the Lyft app just a special-purpose browser for GBFS data files?

	▲	rahimnathwani 4 days ago \| parent [-]
		No idea. I don't use these bikes. But I couldn't resist when GP shared the API endpoints.