Linked by Thom Holwerda on Fri 16th Aug 2013 16:10 UTC
Talk, Rumors, X Versus Y

In the past two months, Microsoft and Google have been bickering over one central issue: HTML5. The Verge has learned that Google is forcing Microsoft to build its YouTube Windows Phone app in HTML5, despite its own Android and iOS versions using superior native code. Although Microsoft has offered to build ad support along with making other tweaks as Google has requested, a full HTML5 app isn't currently possible on the platform.

The difficult thing here is that Google actually has a very good case; it's their API, their service, their rules. On top of that, YouTube publishers - big and small - need to earn money from advertisements too, and incorrect implementations make that harder. Microsoft's mafia practices regarding patents, extorting companies to pay for Android use even though Microsoft has contributed zero code to Android plays a role too. Lastly, Windows Phone is essentially irrelevant with 3% market share - it's not as if Microsoft ever concerned itself with minority platforms.

Still, all this does is hurt consumers, no matter how few Windows Phone users there are. Just work this out, please, you bunch of children.

Thread beginning with comment 569793
To read all comments associated with this story, please click here.
Another view
by zadintuvas on Fri 16th Aug 2013 17:47 UTC
zadintuvas
Member since:
2012-07-23

I think that Google wants to retain control over YouTube. Obviously, it's very hard to do that if you don't make the app yourself. Now, Microsoft built their own app and called it "YouTube". This way Google can not make any changes without asking Microsoft.

If there's already an official HTML/JavaScript API available for everyone and it does not interfere with Google’s ability to make changes to their services, Microsoft should just use it instead of complaining.

Microsoft has built their own Xbox Music app entirely in HTML5. And they promote HTML5 as one of two ways to make Windows8/RT apps. I am surprised if they don't have this capability in Windows Phone 8.

YouTube has agreements with publishers which require them to display ads/compensate for their content. Also they need to ensure that any other restrictions (like, not allowing video on mobiles) are honored. Those are serious obligations and if some 3rd party comes with an app which violates them and potentially causes you problems, would anyone trust them again? Google is offering a way which would let them retain control.

Edited 2013-08-16 17:49 UTC

Reply Score: 4

RE: Another view
by zadintuvas on Fri 16th Aug 2013 17:52 in reply to "Another view"
zadintuvas Member since:
2012-07-23

I’ve checked things on my PC (W8/IE10), Windows Phone, Android and iPad. It seems that non-standard HTML5 video behavior on WP8 is to blame here: “There is also an inherent behavior of Windows Phone where playback of an HTML5 video through a web page opens the built-in media player to host the video”.

Microsoft should fix it.

Edited 2013-08-16 17:53 UTC

Reply Parent Score: 4

RE: Another view
by Soulbender on Fri 16th Aug 2013 20:10 in reply to "Another view"
Soulbender Member since:
2005-08-18

Obviously, it's very hard to do that if you don't make the app yourself. Now, Microsoft built their own app and called it "YouTube". This way Google can not make any changes without asking Microsoft.


Say what? How does Microsoft naming their app YouTube (which is a Google trademark) prevent Google from making any changes?

Reply Parent Score: 2

RE[2]: Another view
by Nelson on Fri 16th Aug 2013 23:10 in reply to "RE: Another view"
Nelson Member since:
2005-11-29

Also worth noting, Apple wrote the original YouTube app. Google recently took over development responsibility of the app.

The Twitter app on WP was similarly worked on by contracted developers by Microsoft before Twitter took over and wrote their own (which replaced the old one).

The Facebook app on WP was an all MSFT thing (contracted out to one of the .NET shops like the Twitter thing, iirc) and then FB collaborated with MSFT on the app for WP8.

There's a few more examples, just none of the top of my head. This is standard practice.

Reply Parent Score: 4