Yes not many use it but if you cut this path off then people will never get there.

Let's not act like things have always been this bad and thus we should just accept it as the norm, because they haven't, the noose is actively tightening as time goes on.

It's not necessary to provide the functionality and enforces the dependency onto he potentially hostile actor (case in point: Microsoft disabling email account of Chief Prosecutor of ICC because US requested so).

It stifles innovation in the future and hurts GrapheneOS right now.

Let me turn the question back at you: why do you think adding unnecessary dependency is better than not adding it?

Does it serve users, governments, service?

Does it anything good for the interested parties or does it only serve Apple, Goggle and the US government?

Its the same as with bicycle paths. Initially - those make no sense, leading from nowhere to nowhere. Give it a few years, and a usable network emerges.

Right now there is serious money and brainpower being poured into sovereign cloud tech. Thanks to the gift of open source and standards, its actually not impossible to create modern systems with zero US dependency.

I fear, though, that as with everything else Microsoft Excel will be the hardest dependency to deal with.

Plus, the net difference is that this gives Google and Apple the ability to kill the ability of individuals to make payments (and tax them) ... do you want that?

(And I would say, compared to having European banks tax them, the answer is not so obvious)

The real issue is, of course, that this moves the burden of keeping phones secure onto Google and Apple, who are very willing to take on that burden in trade for a percentage of all consumer payment traffic in Germany. It's yet another choice between "spend money now to build a government department to secure payments ... or have Apple/Google do that for you". And they're choosing to save a little bit of money in the short term in trade for what is effectively a new tax.