News for hackers. Stuff that matters.
Re:Uber's Design Meltdown by mratzloff on Tuesday February 16, 2016 @07:32PM (#11114238)
Just as software wizards are in other contexts, that would be useful for a new user, but frustrating for a power user who knows exactly what they want and the quickest way to select it.
Re:Uber's Design Meltdown by jaredmiwilliams on Tuesday February 16, 2016 @09:25PM (#11114772)
The experience of a new user in your app can turn out to be a pretty critical moment when it comes to retention. Having a flow specifically for new users is common and does the job of easing them into whatever necessary complexity exists in your default state.
Re:Uber's Design Meltdown by goodplay on Tuesday February 16, 2016 @07:52PM (#11114349)
It doesn't have to be one or the other; include a small switch at the bottom of the screen that alternates between the two representations.
Re:Uber's Design Meltdown by arthurcolle on Tuesday February 16, 2016 @08:15PM (#11114440)
Maintaining one consistent front-end is obnoxious enough from my biased personal experience with the UI/design aspect of building a web app... but I agree that it's probably a weak point that they offer so many disparate options but they are probably just gathering data with what works/what doesn't. Just guessing. I would imagine that eventually we'll see some (more? I don't know if its happened already) closures of the individual Uber product lines