MTA subway status app
Out of context: Reply #3
- Started
- Last post
- 5 Responses
- jetSkii0
I think the entire user interface and feedback is too cryptic for any normal train rider to understand. A question mark as a button is the last thing you'd ever want in an interface. anywhere. users are already filled with a question, so it'd be like answering a question with a question which just becomes annoying. It's too simplistic to be a solution. A mystery box is fun for exploration, but useless for a utility app such as this.
The smiley face is also very questionable. Especially when you get into 3 or more train transfers which is normal. In which case, you can have both smileys and frownies for one direct line to a rider's destination. Also A blue color could be for A,C, or E. and orange for B,D,F,M... based on the above example what if i'm looking at A,F or C, F? Some assurance would surely help iron out these issues. But if being minimal in design outweighs the need for the rider to be assured, then go for it.
On another note, a browser address bar means you are relying on internet access to be fully functional throughout the subway system. This is not feasible for users needing realtime information.
Besides the app that would eventually make no sense, it relies on the input of users to get realtime information on trains? In that case the app itself is unreliable and open for vandalization and users not caring to input the information to begin with.