I'm looking for some feedback on a user-interface design issue in the OneBusAway iPhone app. I figure there are some iPhone designers and users out there that might have some good ideas on how to tackle the problem. The problem is this:
When you are looking at real-time info for a stop, there are a variety of actions you might want to take: add a bookmark, filter the routes, see nearby stops, show the full schedule, see service alerts, report a problem... the list gets longer every day. And so does the list of buttons at the bottom of the arrivals screen:
I think that list of action buttons is getting a little overwhelming. One option is to put them all on a separate screen with a single action button leading things off:
The problem with this approach is that it reduces the visibility of those options. In fact, the very first revision of the app worked this way and I had a lot of reports from users that they couldn't figure out how to bookmark their stop, mostly because the action wasn't very visible.
Another option is some sort of detail indicator on the stop name itself:
Also a number of people have commented on the Service Alert indicator. The image above shows what happens when you have an unread stop-oriented service alert (very visible). Once you've read the service alert, the main service alert element shown above goes away. However, we still include it the action list at the bottom so that you can go back an access the service alert after you've read it.
Our options are limited in some ways, because some normal places you might put action buttons (the upper right corner, the lower toolbar) are already spoken for.
Does anyone have any thoughts on how to deal with this trade-off between an increasing number of actions and the desire to make them visible to the user? Especially in an iPhone app? Maybe you've seen another app that does this well. I'd love your feedback.
Feel free to leave a comment or drop an e-mail at firstname.lastname@example.org. Thanks!