|
|
|
|
|
by josefx
1565 days ago
|
|
> The problem is the ordering platforms enabling this integration without restaurant consent. The lawsuit seems to focus on the history of how that happened a bit. Namely Google seems to have initially tried to sell this API to restaurants directly. Hence the brazen trademark infringement and restaurant impersonation, it was intended to operate with the authorization of the restaurants directly. Only when that failed did they move on to third party distributors that didn't have any right to the trademarks, without changing the now deceptive interface. > I don't think Google even takes a cut! The lawsuit is a bit unclear on that (through information and belief) but also cites alternative revenue streams through ads and pushing more people onto its own payment platform. |
|
...which was a fools errand. It is impossible to expect individual restaurants (_maybe_ aside from large restaurant groups - ie, big chains) to integrate with this API.
To me it seems much more likely that Google pivoted to working directly with delivery operators for practical reasons to make the product functional.
I would also bet that contracts with the delivery operators include a bit about how they will enable this integration and what that means. Perhaps they do not make it explicit enough in the sales cycle (or, didn't in the case of Lime)