I implemented Google One integration in an iOS app. This comment chain is accurate. Users want to pay with Apple (like other app subscriptions) but then your “account” is inside their payments world. Which is super confusing since users (rightly) think they are dealing with their Google account.
Sounds like the analysts and product owners didn't really want to solve this problem. Instead they ticked the boxes, got the bonuses, and the devs never questioned it and just implemented it for fear of being PIPed.
I'm sure there is technically nothing that stopped you from treating this "Pay with Apple" thing as just another payment method inside the google account, except maybe additional complexity and red-tape.
Seen this many times when PMs, POs, and Devs code by features instead of trying to actually solve something. I don't even want to know what mess of a database schema is behind this monstrosity.
