There's something about chicken and egg going on here too. The Chromecast was wildly successful because it rode on the back of an already successful browser (5

There's something about chicken and egg going on here too. The Chromecast was wildly successful because it rode on the back of an already successful browser (50% market share) with support out of the box. It also featured dedicated support for specifics apps and platforms, like YouTube and Android, both within Google's control. Coupled with a low price, this was enough to make the stick sell on its own, and that again compelled developers to implement dedicated Chromecast support in their own apps. In short: Google had both the chicken and the egg. Problem solved. But if Firefox is to make their own free-er stick... They now have 15-16% browser market share which they can leverage and no on-line services which they can use to further increase the value of that stick. If they can make it "Chromecast compatible" that's obviously a different story, but that means Chromecast apps now also need to be compatible with the Gecko rendering engine. Looking at the sorry state of the mobile web in the end of 2015, we can already see a significant amount of developers whose only mobile test-target is Webkit. Some even skip testing Android completely, focusing only on Ios and Mobile Safari. And do we expect developers to bother 1. getting and 2. testing for a Chromecast-compatible device with a sub 1% marketshare when there are already millions of chromecasts out there? To me this just smells like Firefox OS all over. Maybe a good idea, but it's too late, and it probably wont win any developer mind share from the established platforms.