falafel_muncher

> most developers will happily just opt for Apple's system if the rates make sense

The _buyer_ experience with Apple's IAP is mostly good, but I would argue that the developer experience is downright horrible. Working with subscriptions and IAP receipts is clunky. You can only use one of about 100 SKUs, which makes it difficult to offer discounts and customized pricing at the higher price tiers, where the gaps between amounts are quite large. Until recently, it wasn't even possible for developers to issue refunds!

Even if Stripe charged 30%, I would choose them every time over Apple's IAP.

doubtful that stripe has 100,000+ business customers. Kount is another good one, that's what Braintree uses apparently.

You can prevent a lot of fraud by simply requiring both a postal code and the CVV on the card. It's unlikely that a card thief has both pieces of data. (If you steal the physical card, you won't have the postal code, if you buy a database of cards, unlikely that they will have CVV's)

Solution: pay drivers a bonus for the number of 'accidents avoided', or the amount of times they need to grab the wheel after the car sounds the 'take-the-wheel' ping. Drivers will be incentivized to pick-up passengers in more complex areas, which then improves the data and the car learns how to drive better in complex area.

Take the Las Vegas Strip for example. They have a lot of pedestrian bridges for people to avoid crossing streets. Granted, this also works to funnel folks into casinos. However, it would be difficult for a pedestrian to get into the street at some intersections because of fences and barricades. I have to think that most cities will evolve similarly when self-driving cars become commonplace

They still have to work in the rain before gov't allows them on the road though..