This reminds me of my app "Delayed" which I started writing when Android phones were new, and I was commuting by train in Stockholm, Sweden. I worked about a 2 minute walk from the train platform, but I still wanted to know if they were delayed, also I wanted to avoid the proprietary platforms' slowness. I wanted to be able keep working until I knew the train was about to leave.
The mobile networks at the times were abysmally slow and unreliable, the API I was using was slow, basically loading times were unacceptable, I needed the info without delay. No, actually pre-fetched even so that it was working even when offline. I ended up scheduling my app using Tasker so that when I was likely commuting it started updating the timetable in the background. Now I always had instant info available, as good as I could at least.
Plan was to release the app but I eventually realized I would never polish the app to a releasable state, but it still worked 100% for my exact usecase. So I never did get further than a beta test on the Play Store.
The mobile networks at the times were abysmally slow and unreliable, the API I was using was slow, basically loading times were unacceptable, I needed the info without delay. No, actually pre-fetched even so that it was working even when offline. I ended up scheduling my app using Tasker so that when I was likely commuting it started updating the timetable in the background. Now I always had instant info available, as good as I could at least.
Plan was to release the app but I eventually realized I would never polish the app to a releasable state, but it still worked 100% for my exact usecase. So I never did get further than a beta test on the Play Store.