[PeterisP]

Can you elaborate why offline use is something that matters for bus schedules?

I mean, I get the usefulness of wilderness-related apps (e.g. ocean fishing) or various things that could be useful in an emergency like the aftermath of a hurricane, and for these offline functionality matters, but for buses, if you're within a few miles of a bus stop and the buses are running at all, then you're guaranteed to have high-speed cellular internet access and offline features don't matter.

I can imagine being in the middle of some national park where the closest bus is unimaginably far away but I still have mobile internet access, but I really can't imagine a situation where I'd care about buses but don't have internet. Or are USA data plans so small that it's worth thinking about the data usage (as opposed to just latency) of downloading a webpage with timetables?

[pharrington]

> If you're within a few miles of a bus stop and the buses are running at all, then you're guaranteed to have high-speed cellular internet access

This just isn't the case in the United States. There are large swaths of the country that straight up don't have high speed internet in any form.

[busthrowaway]

But those large swaths apparently have a bustling public transit system? Sorry, rural America lacks both decent cell service AND decent busses.

[pharrington]

Certainly, our rural public transit is a catastrophe in it's own right. That still supports the argument that there is a very real use case for offline bus schedule lookup.

edit: /apps/lookup