You may be confused about what the term “core functionality” means. I’ve worked on a couple of pretty major sites, and universally they carefully measure user behavior and any blockers to revenue. And then make cost/benefit tradeoffs about how to improve those measurements.
My suspicion is that the features you wish were implemented are BOTH harder than they appear AND imperfect implementations are worse (in terms of measured usage) than the current lack. For mapping, I don’t know anyone at Uber, but I do know a few geolocation and maps engineers at other companies, and I have some sense of the crazy diversity of confusion that users show when a UI is optimized for even a slightly different use case than they have in mind. I’d bet that many/most destinations are copy/paste or direct link from another app, rather than entered by hand.
That said, even with thousands of engineers (perhaps especially!), there are always blind spots which “everyone knows” we should fix, but it’s just a bit too small for management to notice and slightly too big for anyone to do it unilaterally. These always suck, and the best engineers and managers can recognize it and use their personal influence to get a few of them done.
I think entering payment information is functionality of any online shop and thus have a hard time as not seeing it as part of the core functionality.
On the other hand it getting European IBAN’s easily entered might not be core issue for an Engineer at Amazon.com and there’s no team at Amazon.de which has a lot less developers who’s responsible for it.
I’d bet that many/most destinations are copy/paste or direct link from another app, rather than entered by hand.
Even if that’s true some people might copy-paste streetname + street number and Uber will deliever them to the wrong address without giving them any warning beforehand. In that case showing the user that there are multiple possible addresses seems even more important.
It might be that bringing people to the wrong address isn’t measured in the metrics and reducing the amount of information makes it slighlty faster that people book.
I think entering payment information is functionality of any online shop and thus have a hard time as not seeing it as part of the core functionality.
On the other hand it getting European IBAN’s easily entered might not be core issue for an Engineer at Amazon.com and there’s no team at Amazon.de which has a lot less developers who’s responsible for it.
I’d bet that many/most destinations are copy/paste or direct link from another app, rather than entered by hand.
Even if that’s true some people might copy-paste streetname + street number and Uber will deliever them to the wrong address without giving them any warning beforehand. In that case showing the user that there are multiple possible addresses seems even more important.
You may be confused about what the term “core functionality” means. I’ve worked on a couple of pretty major sites, and universally they carefully measure user behavior and any blockers to revenue. And then make cost/benefit tradeoffs about how to improve those measurements.
My suspicion is that the features you wish were implemented are BOTH harder than they appear AND imperfect implementations are worse (in terms of measured usage) than the current lack. For mapping, I don’t know anyone at Uber, but I do know a few geolocation and maps engineers at other companies, and I have some sense of the crazy diversity of confusion that users show when a UI is optimized for even a slightly different use case than they have in mind. I’d bet that many/most destinations are copy/paste or direct link from another app, rather than entered by hand.
That said, even with thousands of engineers (perhaps especially!), there are always blind spots which “everyone knows” we should fix, but it’s just a bit too small for management to notice and slightly too big for anyone to do it unilaterally. These always suck, and the best engineers and managers can recognize it and use their personal influence to get a few of them done.
I think entering payment information is functionality of any online shop and thus have a hard time as not seeing it as part of the core functionality.
On the other hand it getting European IBAN’s easily entered might not be core issue for an Engineer at Amazon.com and there’s no team at Amazon.de which has a lot less developers who’s responsible for it.
Even if that’s true some people might copy-paste streetname + street number and Uber will deliever them to the wrong address without giving them any warning beforehand. In that case showing the user that there are multiple possible addresses seems even more important.
It might be that bringing people to the wrong address isn’t measured in the metrics and reducing the amount of information makes it slighlty faster that people book.
I think entering payment information is functionality of any online shop and thus have a hard time as not seeing it as part of the core functionality.
On the other hand it getting European IBAN’s easily entered might not be core issue for an Engineer at Amazon.com and there’s no team at Amazon.de which has a lot less developers who’s responsible for it.
Even if that’s true some people might copy-paste streetname + street number and Uber will deliever them to the wrong address without giving them any warning beforehand. In that case showing the user that there are multiple possible addresses seems even more important.