4 ms·
Exactly. Outsourcing your main tech stach isn't exactly competing with Uber. It's easy to tell them apart. Which team has a properly restful API available to t
by seivan 11y ago
Exactly. Outsourcing your main tech stach isn't exactly competing with Uber.
It's easy to tell them apart. Which team has a properly restful API available to the public.
- LunaSea 11y agoIt's amazing to me that you think that anybody (besides developers) will care about REST API design rather than the service offered by the driver.
- repomies691 11y agoI don't care about the REST API, but I care how well the app works etc. It doesn't sound trivial to me. Showing the locations of the car and the customer in real-time, routes in real-time, having all the communication systems working all the time, the reputation system etc.
- Q6T46nT668w6i3m 11y agoWhile I agree with conclusion, Uber, et al. doesn’t actually show real-time locations and the communication system is error prone.
- matwood 11y agoIt looks like real time locations when I've taken uber, unless you mean not real time as in slightly delayed time to get GPS, go to uber and then back to my phone.
- seivan 11y agoIt matters to me, it tells me tech isn't second hand unlike EVERY OTHER TAXI COMPANY with their shitty unreliable apps. It's a litmus test. Obviously your milage may vary but I've taken more Uber per month than I have taxis per year before Uber came to Stockholm. They made it so available.
- danpalmer 11y agoUber's API is not RESTful. It's JSON over HTTP, with some correct verb usage, but that's all.
- seivan 11y agoYou're absolutely right. But I can't figure out how I would have done it better myself. Something I would have experimented with is price being a query parameter instead of a nested route. https://developer.uber.com/docs/v1-estimates-price https://developer.uber.com/docs/v1-estimates-price Though I appreciate the proper verb usage and not seeing shit like post /v1/bookCar GET /v1/getCars shudders