Live data from Hacker News

Introducing the Uber Request Endpoint

devblog.uber.com

11–20 of 41 posts

Re: Introducing the Uber Request Endpoint

#11

We spent a weekend contemplating fun uses for the Uber API. Here are a couple ideas that we abandoned - feel free to use as you wish: * "Bar roulette" where you would hit a button, an uber would show up, then take you to a random bar sourced from Yelp. * Last-minute ticket sales to events (e.g. in the hour before they start) that include transportation * Having bars or clubs offer to drive people there for free and b…

That third one reads like something out of a Gibson novel. Might work best with a pre-defined group of people (e.g., models in an agency) or something similar.

"like something out of a Gibson novel.", "models in an agency".

While not politically correct, it would be interesting to run an outcall escort service with this. Throw in an AirBNB API...

Disclaimer: The above is just a thought. I do not condone this use case.

Re: Introducing the Uber Request Endpoint

#12
post #7

I worry that they're just going to follow Twitter's lead: build an API, get developers to work on interesting new ideas, pull in the good ones and the slowly squeeze out devs by locking up the API.

This is completely different. Usage of the API will translate directly to more rides on the platform and more $$ for Uber. The company will have every incentive to keep developers happy if apps are increasing ridership.

Re: Introducing the Uber Request Endpoint

#16

Earlier quoted context omitted.

That third one reads like something out of a Gibson novel. Might work best with a pre-defined group of people (e.g., models in an agency) or something similar.

There could be all kinds of uses. Imagine a product launch event - "We need to pack a room so the press is impressed. Want anybody and everybody - tell them we have free food."

That'll get them to the location, but how long will they stick around.

Re: Introducing the Uber Request Endpoint

#17
I admit this was my one complaint about their API when it was released, since it meant I couldn't do thinks like write Uber for Glass. Their branding document is very detailed and handy to make their buttons look good on mobiles too, so I liked the quality of their work otherwise. Since they fixed it I'll have to take a look at doing the hackathon, I guess. Although maybe I'll have to put it on a watch instead of a Glass since Glass is dead.

Re: Introducing the Uber Request Endpoint

#18
post #10

The Uber API is pretty nice to work with. I built a mobile-web surge avoider: http://nomoresurge.divshot.io/client/ If you load that up on your mobile phone you can search for the location nearest to you with low or no surge, and then deep link into the Uber app to actually call the car. Now I can implement requests directly, which is very cool.

I'd definitely use this. I've noticed that I can often change location by a couple of blocks to avoid surge charging

Re: Introducing the Uber Request Endpoint

#19

Earlier quoted context omitted.

There could be all kinds of uses. Imagine a product launch event - "We need to pack a room so the press is impressed. Want anybody and everybody - tell them we have free food."

That'll get them to the location, but how long will they stick around.

As long as the food is free and they are not yet satisfied. Drip feed them.

Re: Introducing the Uber Request Endpoint

#20

Earlier quoted context omitted.

That third one reads like something out of a Gibson novel. Might work best with a pre-defined group of people (e.g., models in an agency) or something similar.

"like something out of a Gibson novel.", "models in an agency". While not politically correct, it would be interesting to run an outcall escort service with this. Throw in an AirBNB API... Disclaimer: The above is just a thought. I do not condone this use case.

This is what chatroulette should have turned into.
Post reply on HN