Most likely different incentives and platform culture.

Customization isn’t that big on iOS, other than the occasional viral fad, so there’s less interest for custom keyboards and in return less development spent on it.

Monetization of custom keyboards is also really hard and due to limitations on tracking and collecting data the incentives that Android has don’t really exists on iOS.

So what you end up with is a handful of custom keyboards often by big players that have bags of money to throw at it or as a companion to a regular app (e.g. Grammarly, GIF apps) to fulfill a specific function.

They’re right about browsers, but jumped the shark on keyboards.

Custom keyboards come with some rules and limitations for obvious reasons, but they’re by no means the system keyboard in disguise like how browsers are all WebKit under the hood.

Here’s documentation on custom keyboards: https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/CustomKeyboard.html#//apple_ref/doc/uid/TP40014214-CH16

The scandal didn’t lie in following court orders, it lied in the marketing and the fact that the French ToS lacked any nuance to indicate that it would even be a possibility that ip would be logged.

Furthermore, even when dealt with court orders, other companies that don’t tout privacy to be one of their core values, have chosen to fight such orders in court.
Proton could’ve at least tried to show that they were putting their money where their mouth is, by challenging the order.

Between this and the IP logging scandal, it seems that they’re going downhill fast.

Pro tip: if you do insist on using Google scroll to the bottom until you see a notice like the one below.

You can then click on the complaint to see the URLs that were removed.

They’ve wisened up a bit and now require a (throwaway) email to access the links, but chances are that if you’re looking for something more obscure, the link you seek is still there.