3 ms·
But then the driver is at the mercy of the aggregator App. It's the same problem as working with Uber or Lyft directly, really.
by JMTQp8lwXL 7y ago
But then the driver is at the mercy of the aggregator App. It's the same problem as working with Uber or Lyft directly, really.
- spookthesunset 7y agoSetting aside the rider... in my world Uber and lyft would have open apis so third party apps could somehow aggregate the two services. These apps would be pretty basic and just let the driver accept rides from either service from within the same app. Dunno if this is actually a problem though...
- pishpash 7y agoAggregation already exists for both riders and drivers. For riders there is Google Maps. For drivers there is Mystro and the like.
- basch 7y agoI'm thinking more like email, ActivityPub, XMPP, or hate to say it, blockchain. There doesnt need to be an aggregator App if its a federated protocol or a shared database. A blockchain would be a central store of truth regarding ride history and reputation. Your reputation would build across access clients. If a client doesnt keep innovating, and there is demand for more features, newer ones would come along, without throwing away the database and starting over.