I use Citymapper to use Citibike, and it has the following big flaws:
- Reloading the app, it never remembers I was on the biking screen, and always goes to the main screen. Minor detail, but annoying, and so easy for them to fix!
- Every time I move the map even slightly, it removes all bike stations from the map and queries the API again for a new set of stations, even if the last request was only five seconds ago. If there's any wireless interference, it complete destroys the functionality. I mean, cache the station locations at the very least! And don't hide the old data while waiting for the new data, if it's less than a couple minutes old.
- The screen real estate devoted to the map is only ~50%! The bottom third is taken up by a totally unnecessary textual list of stations, which can't be hidden
- And you can't even rotate the map!
Granted, it's a million times better than the default Citibike app. But it's still got a ways to go to achieve "ideal" UX.
- Reloading the app, it never remembers I was on the biking screen, and always goes to the main screen. Minor detail, but annoying, and so easy for them to fix!
- Every time I move the map even slightly, it removes all bike stations from the map and queries the API again for a new set of stations, even if the last request was only five seconds ago. If there's any wireless interference, it complete destroys the functionality. I mean, cache the station locations at the very least! And don't hide the old data while waiting for the new data, if it's less than a couple minutes old.
- The screen real estate devoted to the map is only ~50%! The bottom third is taken up by a totally unnecessary textual list of stations, which can't be hidden
- And you can't even rotate the map!
Granted, it's a million times better than the default Citibike app. But it's still got a ways to go to achieve "ideal" UX.