search

oscarpan / cogs121

Triton Transit Application by Team DJ MO
0 stars 1 forks source link

Milestone 3 feedback #2

Open kandarpksk opened 7 years ago

kandarpksk commented 7 years ago

Write comments below, not in a separate thread.

hcqpham commented 7 years ago

K6 Hookah:

Feedback: You have a solid idea, but what you have right now isn't necessarily any different from Google Maps. I wish there were different functionalities to separate your app from other apps on the market.

Claire: Here are some ideas that I bounced off of one of your team members for potential functionalities for your application:

April I like that the app has a specific use case, which is for UCSD students and it provides information (how crowded shuttles are) that is useful and not present anywhere else I wish the users could add stops to their route in order to calculate the total amount of time it would take and the optimal routes available to travel to multiple places in the same trip.

Devon I like that the app provides crowd information in order to plan your day and to travel more efficiently.
I wish that this was more significantly different than already existing apps. It seems more like a new feature(s) for those than a new concept.

Zhiyu: I like: The concept of combining the traffic on the bus and ETA of getting to the bus. I wish: Recommended time for students to go to the bus. As every quarter, students' schedule is almost fixed. Every day at certain time, the bus must be very crowded. It would be great to notify student what is the good time to go and when to avoid the traffic.

sandrahluo commented 7 years ago

Team K8 Feedback

Ryan: I like how you are clearly aware of a feature that other systems are lacking (percentage of bus that is full) and that you understand the contextual situation where you would use an app like this.

I wish there was more of a unique value proposition of the app though – it seems like a majority of the features are available on Google Maps, and that is an app I already have across all my platforms and is easy to use. Is the value add of "percent filled" enough to convince people to use your app?

Sandra: I like the research that you've done for finding relevant APIs for your project. I like the data visualization of peak times for ridership.

I wish there was an option to save "home" and "work/school" locations, so I don't have to type them in every time I use the app. Also ditto Ryan's "wish" -- I use an app called Moovit and am pretty satisfied with it.

Greg: I like that the app idea consolidates a lot of information that is spread out over multiple sources. They seem to have considered where they will get all the data to make a the predictive element of their app work.

I wish that the app allowed the user to compare some other methods (walking or biking) to taking the bus. I would also challenge them to come up with some visualization for bus fill and wait time that can be more integrated, doing mobile means they have to be more creative with information since the screen is smaller. Showing a map, graphs, any text separate will each up too much real estate.

Yacoub: I like that they have identified a problem clearly and seem to have a good grasp of their users' behavior and wants.

I wish I knew how they are collecting the percent full data. If they can't do that, their app is not useful

kandarpksk commented 7 years ago

It's a good idea, but it's not clear where you will get your data from (how long the line is, to what extent are buses crowded). Think of what you could pivot to, since there is no novelty in the case that this data isn't available. Also, avoid pitching it as student centered, making it a more general transit app.

PS: Make sure to iterate on and not commit to the sketches early on (they are just to make the idea concrete enough to present for feedback). Feel free to ping me on Messenger to discuss.