Nice character assassinations, but whose fault is it where ChromeOS is pioneering the field, and is alone in writing and implementing these sorts of standards?

Nice character assassinations, but whose fault is it where ChromeOS is pioneering the field, and is alone in writing and implementing these sorts of standards? You've conveniently omitted the wider effects of Apple's monopoly from this analysis. There's plenty of evidence of the actions they've taken to wall-garden anything and everything possible. For example, let's talk about NFC. It's been acknowledged that NFC adoption by major third-party apps on Android is severely constrained by the notion of feature parity with iOS; meaning, since NFC cannot be done on iOS in an app, it's almost pointless to support NFC just on Android. About a decade ago, I could pay at Trader Joe's and other NFC terminals for my groceries directly with my Wells Fargo app; but, today, I cannot do that, because Wells Fargo no longer supports NFC in their app. Many other vendors in many countries went directly to the QR codes given the realities on the ground. (If Apple had unrestricted NFC access, would Walmart forgo NFC?) Yet now you're telling us it's Google's fault that "noone" wants to implement WebNFC, depriving it of the standards status, due to the lack of the independent implementations? Now, let's talk about Mozilla. You're implying that Google is Mozilla's master, because they pay them half a billion a year. But is Mozilla allowed to ship a proper browser on iOS? And, even if they did, would they have a capability to access NFC, and implement WebNFC? Whose fault is that if not Apple's? So, who exactly besides Apple and Google are even capable of implementing WebNFC given the realities on the ground? Because clearly that's not Mozilla, since Apple won't let them, in more than one way. And, BTW, what actual solutions or alternatives do you propose? Simply not have any standards for these things at all, since security and privacy? Because without these "proprietary" "standards" that no other vendor wants, or has the capability, to implement, what exactly are we left with? Are you serious in implying that Apple's fully proprietary APIs are better than Google's open standards that noone else wants to implement, simply because of the Apple/Google duopoly, since noone else is big enough, and since Mozilla has abandoned Firefox OS and Boot2Gecko?