Hacker News Reader

> Blocking on this basis alone is a double standard from Google. As others have pointed out, the iOS app developed by Apple never showed ads, even if the videos were monetized. Google never unilaterally revoked Apple's API access over it.

It has been mentioned else where in the thread that apple had licence from google to use youtube without ads and when that licence ended they removed the app from the market.

>Though one could argue that they did and that's why iOS 6+ doesn't include it. But that doesn't explain why Apple TV, to this day, still plays all videos—even with required monetization—without ads. Why is it okay for Apple to do this, but not Microsoft? Why won't Google license YouTube API access on the same terms?

Apple may very well have a licence for this as they did previously with the iphone app.

> As above, why won't Google license this to Microsoft on the same terms as other competitors?

The article does not even say if Microsoft has been seeking such or if Google has denied them. If they are/have been seeking then the author of the article should have included this fact to make their argument stronger, but if it is there I missed it.

> Heck, there's even a third-party app for iOS called Jasmine[1] that is a native app (embedding just the HTML5 video player inside the app as y2bd points out below) and uses YouTube branding. Why is Google making it more difficult for Microsoft to do the exact same thing? We're clearly not getting the full story from anyone here.

Big players get more attention because they have a larger effect. It would be unprofitable and unproductive for its long term survival for google to pay equal attention to small players transgressing rules as they do larger players.

I believe, and I could be wrong, that the iOS YouTube app was developed jointly by Apple and Google back when iOS first came out in 2007, when YT and mobile video was in an entirely different place than it is today.

Google signed some sort of license with Apple for access to YT via that app, and when it was up, they pulled the app (despite there being no official Google YT app at the time) from iOS. It's very possible that the ATV app for YT is still under some sort of license with Google, which is why it can play videos ad-free.

It all comes down to the fact that iOS is too significant source of users to give the cold shoulder. Windows Phone is still sufficiently small fraction of the market, that Google has more interest in degrading the Windows Phone OS instead of earning from the additional users.

I think this is purely a game of numbers, and if/when WP gets big enough that the additional income from eg. youtube outweighs the income generated from users who picks android next time.

A nitpick, but although Jasmine is a native iOS application, when it comes to actually playing a video, it opens a YouTube video embedded in a web view. That is why you see the YouTube player for a brief moment before the video starts.

That's true; I updated my comment to clarify that. If that's the difference between Google being okay with it and not, I guess I don't see where the chasm of difference is:

* Microsoft claims they've enabled ads on YouTube videos. How, if they're not using the same technique as Jasmine?

* If they are using the same technique as Jasmine, why is that not enough? Why is Google still saying (or at least Microsoft is claiming that Google is still saying) the entire app must be HTML5?

* If the technique Jasmine uses does, in fact, satisfy Google's "HTML5" requirement, but for some reason Microsoft isn't using it (but somehow is playing ads anyway), why doesn't Microsoft just do it? Embedding a web view into a native app isn't exactly rocket surgery: why do they claim it's technically difficult and time consuming?

Assuming they figured out how to display ads without using the embedded HTML5 player, a guess I can offer (as a WP user) as to why they don't is that if they do, the video would launch in the default webview video player, which is honestly pretty terrible. You can't even scrub through videos. The MS-built YouTube application however had a much-more featured video player[1].

Quite a few WP applications that are video-centric (such as the non-MS YouTube apps, Netflix, etc.) use their own much-improved video player. Even Microsoft provides a better video player for usage in WP/W8 applications[2]. Making an improved video player on a per-app basis probably would require a lot less overhead than changing the system-wide video player.

This is all just a guess of course.

[1] http://www.windowsphone.com/en-gb/store/app/youtube/dcbb1ac6..., check the screenshots

[2] http://playerframework.codeplex.com/

My gut tells me that everything falls down to your last bullet, i.e. Google does not care if the full app is HTML5, but they want the an HTML5 YouTube player with appropriate DRM to be embedded in the app so they have full control on the ads and other stuff they are serving, and Microsoft is deliberately trying to avoid it and misleads everyone into thinking that they require full HTML5 app to be implemented.

You know what? If it is time consuming to implement, it's Microsoft's problem, not anyone else's. Lots of people would be happy to get shitload of money from Microsoft and assemble a team to implement it if their problem is difficulty and they are so generous to be willing to pay cash, as they brag about in their blogpost ("...at Microsoft's expense...").