> If I could <use standard protocol or API reliably>, Google would earn more of my money. This is wishful thinking. Across their product line Google extends an

> If I could <use standard protocol or API reliably>, Google would earn more of my money. This is wishful thinking. Across their product line Google extends and abuses common standards, or more frequently rolls their own parallel which dominates by virtue of convenience and userbase. Try using an organizational (GSuite) Google Calendar account from any app that isn't Google Calendar, and it'll quickly become clear that this use-case simply isn't optimized for. Simple things like sharing calendars with write access don't work without finding a particular settings page that hasn't been updated since 2009. There is also no API for room reservation systems if an organization is using Google Calendar for those that I can find. And of course, need I mention the casualties of RSS compatible Reader and XMPP/Jabber compatible GTalk? The parallel to Microsoft's 90s EEE modus operandi is plainly evident. But with Google, it even stretches into web standards. Google has shown little interest in being a good citizen of an open protocol-based ecosystem, except at first to get new users into the walls before they close the gates.