MTA subway status app
- Started
- Last post
- 5 Responses
- ctcliff
Working on an entry for the NYC Big Apps 2.0 (http://nycbigapps.com/) contest and was hoping to get some early feedback on my concept.
The goal of the project is to be a simple, cross-platform data visualization of transit status for locals who already know which trains they ride. The app will retrieve real-time status of multi-line trips based on user input.
The user interface consists only of the browser address bar. For example, suppose the user's commute always consists of the A and the F. The user would enter "/A-F" in the address bar and see something like this:
The user receives feedback in the form of an smiley face indicating the state of their requested transit service. Clicking the "?" button will provide detailed information on the service status.
You can play around with a rough demo here (this example is fully JavaScript so you need the "#"):
http://christophercliff.github.c…
http://christophercliff.github.c…
http://christophercliff.github.c…Any feedback is appreciated!
- ctcliff0
As a technologist, I can appreciate the simplicity of a purely text/HTML based solution (also keeps the weight down), but I'm wondering if that will resonate with normal people. Would it benefit from more expressive illustration?
Also, the face metaphor isn't universal. It starts to break down if you enter more than 3 trains (do people actually make 3 transfers?) and a single route sorta gives you a cyclops looking thing...
- CockDiesel0
I kind of like the three eyed monster
- Could maybe make monster illustration for 3 eyes and spider or something for 4...ctcliff
- 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.
- ctcliff0
Thanks for the feedback. I want to elaborate on a couple of your points.
I, and I presume a lot of other people, tend to ride the same trains over and over. If there is an outage, I probably won't find out about it until I'm on the platform. I can check the status before I leave the house on mta.info, but their visualization is cluttered and not customizable. This goal of this app is to provide a quick yes/no visualization of only the trains I care about.
The data is provided by the MTA and has some limitations. One, it's grouped by color rather than individual train, so you can't really look up info on the "A", only the "ACE." The question mark is there to give the full text explanation (like you would see on an poster on the subway platform).
Also, there would be a project homepage with an explanation of the app and how to use.
Agree this is kind of a niche solution, but I think it's an improvement on the existing notification system. Any thoughts?
Also, if you're making that many transfers, you should consider moving:
- jetSkii0
I think your presumptions are correct, many people ride the subway system, and they'll ride the same trains over and over. Limiting yourself to your niche demographic, I can also presume that those same people will also travel to other new destinations from time to time trying to get to appointments on time for work, business, school, social, play, etc... That's when they'd really need your app.
It's not much a question of moving. If you want to go from queens to brooklyn, those are the steps people have to take. Not everyone is a hipster who lives on the L line or one stop away from the city. People travel for many reasons outside the scope of what you do, which is travel from home to... and back. I'm sure many app designers would love it if the world could change to suit their application, but the sad part is that's not really a feasible solution, and your app would just get shot down.
I would rather have an app that tells me yes or no, rather than a goofy smiley face or frownie face. Especially since many people might not see the cryptic smile. Which then a nose, cheeks, color, eyelashes, might help solve that issue. It's cute for a couple of seconds til the idea just dies because I can't tell if the app even knows what train line i'm interested in. Can you believe that some people can't even tell the difference between the orange and yellow lines? It's a good thing they can read though. There's just a huge lack of consideration here for the people you want to develop this app for.
As far as improvements, i can't say that it is better than MTA's current solution because you offered additional problems which just makes your app equally as un-usable and un-friendly.