Four score and seven years ago our fathers brought forth on this continent, a new nation, conceived in Liberty, and dedicated to the proposition that all men are created equal. Now we are engaged in a great civil war, testing whether that nation, or any nation so conceived and so dedicated, can long endure. We are met on a great battle-field of that war. We have come to dedicate a portion of that field, as a final resting place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we should do this. But, in a larger sense, we can not dedicate -- we can not consecrate -- we can not hallow -- this ground. The brave men, living and dead, who struggled here, have consecrated it, far above our poor power to add or detract. The world will little note, nor long remember what we say here, but it can never forget what they did here. It is for us the living, rather, to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced. It is rather for us to be here dedicated to the great task remaining before us -- that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion -- that we here highly resolve that these dead shall not have died in vain -- that this nation, under God, shall have a new birth of freedom -- and that government of the people, by the people, for the people, shall not perish from the earth. Abraham Lincoln November 19, 1863
Sandra: Hexagons cover way too much land for the scope. If the idea is to allow people to walk to different places for a lower rate, it's not really encouraging if the next hexagon is like a 20 minute (~1 mile) walk away. Hope that this will be considered in your next steps and that you will be able to implement more of the data functionality.
Greg: The next feature I want to see is data filling the hexes from the api. The hex system to me can be a bit foreign and distracting. They mentioned issues with conflicts between Uber and Lyft and how they segment the maps, but it would be nice if hexes merged together if they are similar pricing or some way of removing the clutter of the hex while still keeping the information they are intended for.
Ryan: I like the progress so far, awesome work! I am a little confused about some of the buttons, but I’m sure they will be better labeled in time. I would like to see the ‘points’ be converted into actual info about surge pricing, that would help the app make a lot more sense when I pick it up
Yacoub: I would like to see some kind of understanding as to what the points refer to. How can I use those tomake the best decision about where to call an Uber or Lyft?
I would like to see the estimated duration of the surge in addition to the application offering me an alternative hexagon if I am in a red hexagon zone. Ideally, it would reroute me to a cheaper location within walking distance and price comparison between Uber and Lyft. Cool concept!
David Zech
I'm confused as to what the hexagons meant at first, I thought it was a board game at first. Maybe change the opacity of the hexagon lines to make it less noticeable? It kind of steals the show from the real meat of the app, which is the ride sharing information. To be more specific, the lines are kind of harsh. Next feature I would like to see is filling the estimated fare cost for a region.
Max Chen
I would like to see some explanations of what the hexagons mean and correspondingly hopefully get the interface more optimized for mobile. I feel like if I were to use the app, it would mostly be on the go and on mobile instead of on a laptop so the mobile interface is very important to me.
Oscar Pan
I would like to see the current location of the user next. That way, with geolocation, users can quickly navigate to the hexagon corresponding to their current location and figure out which way to get to a lighter colored hexagon. Perhaps suggestions on if they should wait or take Uber vs Lyft vs another ridesharing app would be helpful. I don't know if it makes sense but perhaps if you are traveling far from a surge location, the app can suggest to take an Uber to a close non surge location and then take another Uber from the non surge location to the final destination.
Team K8
Sandra: Hexagons cover way too much land for the scope. If the idea is to allow people to walk to different places for a lower rate, it's not really encouraging if the next hexagon is like a 20 minute (~1 mile) walk away. Hope that this will be considered in your next steps and that you will be able to implement more of the data functionality.
Greg: The next feature I want to see is data filling the hexes from the api. The hex system to me can be a bit foreign and distracting. They mentioned issues with conflicts between Uber and Lyft and how they segment the maps, but it would be nice if hexes merged together if they are similar pricing or some way of removing the clutter of the hex while still keeping the information they are intended for.
Ryan: I like the progress so far, awesome work! I am a little confused about some of the buttons, but I’m sure they will be better labeled in time. I would like to see the ‘points’ be converted into actual info about surge pricing, that would help the app make a lot more sense when I pick it up
Yacoub: I would like to see some kind of understanding as to what the points refer to. How can I use those tomake the best decision about where to call an Uber or Lyft?