Laverii
commented
7 years ago Team 19; Team Pokeboops, K1
Peter: I like the idea of being able to pick your preferences including between walking and services. I really like the last idea where it filters everything out before displaying your route. What I'm confused about is which service is displayed to / used by the users in this app. I'm also confused on whether it has to be a hexagon or it could be any shape that represents an area, but otherwise it is a wonderful idea.
Inkan: I was confused on how the app can measure the prime time/surge in certain areas? Also must the user use Uber or Lyft or is public transportation an option to the users? How would showing the less crowded time different than Google Maps showing the fastest route? I think the fact this app is helping users avoid crowded areas to get to somewhere faster is a great idea though, it can be very helpful to users!
Austin: I was confused by the overall interaction between strictly navigation (google maps, as mentioned) and services that physically get a user from point A to point B (Uber and Lyft). Is this application meant to just show the most cost-effective route (based on money, time, energy/willingness, etc.) or does it further order them and actually help the user get there? I like the consolidated graphics (hexagons to represent prices, sliders to visualize trends) in the map interface, since there is a lot of information that has the possibility of cluttering the screen and overwhelming the user.
Andrew: I was confused by the UI a bit. If I'm understanding it correctly, this is for users that are debating on whether to wait for a ride or walk to a particular destination or waiting for a better time to fetch a ride? I think this is a super cool idea though. I wonder if an non-UBER/Lyft service could be noted too like if a friend were to drive over, or if they had a DD that could drive them.
Sandra: Prototype 1: I'm not sure what the last screen is telling me or when it would be displayed to me. Prototype 2: Would be nice to include Lyft Line and Uber Pool options since I usually use those options. Perhaps include a bus option if they are near me and I would wait < 5 minutes for them. Not sure what 44% savings means-- savings compared to an Uber I take from my current location? What does the "-" suggestion mean? Prototype 3-1: Not a fan of having to open an external app (Google Maps) if it's avoidable. Prototype 3-2: It's not clear where the alternate locations are on this prototype. Is it possible to get the data of knowing when the surge will die down? Prototype 4 (1): What would the (i) button do? What kind of information would it show me? Prototype 4 (2): Would be helpful to include street names. What is the radius of these hexagons? Are hexagons the most user-friendly way to display this information and does the data you get lend itself to being displayed in this grid-like format?
Yacoub: Prototype 1 doesn't show a preview of the better options, so it makes me wonder if there are any.
The layout of Prototype 2 is unclear.
Prototype 3-2 is very similar to 3-1, but the zone view is much more intuitive. Users might be upset to be sent to a specific point as opposed to a zone. Additionally, the filters don't seem like a value add. I imagine there aren't that many different price zones in your proximity that you need filters. You may as well just show the user all of their options.
Link to Prototype 4 does not work.
Ryan: (1) I can’t really tell what you click or what any of the menu options are. It seemed like other prototypes let you segment rides but I don’t see how to do that here
(2) Is this all one screen? Are the suggestions and map their own screens or are they combined? What platform is this? I can’t tell if I’m looking at web or mobile.
(3-1) I’m confused what functionality this adds on to Uber. It seems like your app lets you filter surge charges, but you would be able to see what the effective surge is if you were using Uber itself. It’s definitely not clear what value add this platform would have based on the prototype. Even the numbered steps seem to have me just call an Uber.
(3-2) So the value here is a bit more clear than any of the other prototypes, and I think I get what the app actually does from this – it seems like the idea is piecing together Uber rides to make an overall cheaper ride through multiple trips. Still, I believe that surge pricing is constantly changing and I’m not sure you can predict it this well. 5 minutes later all of the Ubers will have moved, and this will surely change the price. It also seems odd that across the apps, there isn't an agreement on how surge zones are divided – are you sure this works?
The 4th linked paper-prototypes has an expired URLs
Greg: 4) I think the UI lends to a desktop, however I think that the users who will want to min/max their Uber or Lyft prices will be on mobile devices. The hexagon format I do not think will lend to the actual distribution of prices across a city. The data itself should help define the spaces based on pricing.