robert_cringely
Columnist

No winners in Google-Microsoft spat, but one clear loser: Users everywhere

analysis
Aug 16, 20135 mins

Not content to fight over, er, everything, tech giants battle over YouTube and HTML -- at the expense of the user experience

They are the rock-’em-sock-’em robots of high tech. But no matter how many swings they take at each other, neither Google nor Microsoft is ever likely to land a knockout blow.

Last May, Microsoft released a YouTube app for Windows Phone that allowed users to download videos while not displaying those annoying YouTube ads. Google immediately sent Microsoft a cease-and-desist order and made Redmond take the app down.

[ For a humorous take on the tech industry’s shenanigans, subscribe to Robert X. Cringely’s Notes from the Underground newsletter. | One can not live on snark alone. For a quick, smart take on the news you’ll be talking about, subscribe to InfoWorld Tech Brief today. ]

Earlier this week, the new, improved YouTube app returned to the Windows Store. This one shows ads, forbids downloads, and tacks on a few other nifty upload features. Google immediately blocked it, saying it still failed to meet its terms and conditions — primarily, that it was not written in HTML5.

Don’t hold back

Now Microsoft has taken the spat public. In an extraordinarily lucid, pull-no-punches blog post yesterday, Microsoft Deputy General Counsel David Howard wrote:

We temporarily took down our full-featured app when Google objected to it last May, and have worked hard to accommodate Google’s requests. We enabled Google’s advertisements, disabled video downloads and eliminated the ability for users to view reserved videos. …

There was one sticking point in the collaboration. Google asked us to transition our app to a new coding language — HTML5. This was an odd request since neither YouTube’s iPhone app nor its Android app are built on HTML5. Nevertheless, we dedicated significant engineering resources to examine the possibility. At the end of the day, experts from both companies recognized that building a YouTube app based on HTML5 would be technically difficult and time consuming, which is why we assume YouTube has not yet made the conversion for its iPhone and Android apps.

For this reason, we made a decision this week to publish our non-HTML5 app while committing to work with Google long-term on an app based on HTML5. We believe this approach delivers our customers a short term experience on par with the other platforms while putting us in the same position as Android and iOS in enabling an eventual transition to new technology. Google, however, has decided to block our mutual customers from accessing our new app.

Howard added:

It seems to us that Google’s reasons for blocking our app are manufactured so that we can’t give our users the same experience Android and iPhone users are getting. The roadblocks Google has set up are impossible to overcome, and they know it.

Hmm, that sounds awfully familiar. Where have we heard that kind of thing before? Oh yeah, from Microsoft. Just two days ago I wrote about how Redmond would allow only a hobbled Dropbox app into its Windows 8 store. I’m sure Microsoft had some technical reasons why it was too difficult to fully enable Dropbox in Win H8. I’m also certain the real reason is that Microsoft really wants you to use SkyDrive.

Google’s official response to Howard’s post:

We’re committed to providing users and creators with a great and consistent YouTube experience across devices, and we’ve been working with Microsoft to build a fully featured YouTube for Windows Phone app, based on HTML5. Unfortunately, Microsoft has not made the browser upgrades necessary to enable a fully-featured YouTube experience, and has instead re-released a YouTube app that violates our Terms of Service. It has been disabled. We value our broad developer community and therefore ask everyone to adhere to the same guidelines.

Translation: Neener, neener. I know you are but what am I? See ya, wouldn’t want to be ya. And so on.

Agree to disagree

There’s quite a long history of this kind of sniping between tech giants. As Cnet’s Daniel Terdiman recounts, we’ve seen similar tussles over Instant Messaging (AOL, Yahoo, and Microsoft), Flash (Adobe and Apple), and Twitter and its legions of third-party developers, most explicitly Instagram after it was acquired by Facebook. In some cases, as with IM, the parties ultimately realized that interoperability made a heck of a lot more sense for everyone involved. In other cases (like Flash), the parties will carry this dispute to their graves.

(Personally, though I agree with Apple that Flash mostly sucks, I am often frustrated by my inability to view Flash media on my iPad. Just sayin’.)

Terdiman concludes, rightly I think:

What the technology industry’s long history of interoperability skirmishes makes abundantly clear is that things never change, no matter how much the industry’s giants pay lip service to putting users first. When profits and control over users’ data and loyalty are at issue, more often than not, it’s the users themselves who end up as collateral damage.

Yep, what he said. The problem of course is that technology companies are insatiably greedy. They want to own everything and everyone. As a result, they stretch themselves across too many platforms, taking one strength (like desktop operating systems or search) and turning it into a series of weaknesses. We saw it happen with Microsoft in the 1990s, and we’re seeing it now with Google.

When you try to be all things to all people, you risk being nothing to no one. That seems obvious to me. Why isn’t it obvious to them?

Should Google and Microsoft play nice for the good of the user community? Post your thoughts below or email me: cringe@infoworld.com.

This article, “No winners in Google-Microsoft spat, but one clear loser: Users everywhere,” was originally published at InfoWorld.com. Follow the crazy twists and turns of the tech industry with Robert X. Cringely’s Notes from the Field blog, and subscribe to Cringely’s Notes from the Underground newsletter.