Unity promotes itself as the multi-platform middleware of choice for game developers, however, it has a few concerns on its hands. The first relates to iOS and is a bit beyond the scope of this article; it's sufficient to say the company is working hard to meet the requirements of Apple. The second revolves around Unity's web plugin, which until recently worked fine in Chrome but as of the browser's most recent update, is disabled by default.
Unity's web plugin relies on NPAPI to work, so when Google killed it in Chrome, any games using the plugin stopped working. For now, it can be turned back on using Chrome's experimental settings, but come September, users will have to switch to an alternative such as Internet Explorer or Firefox to enjoy Unity-created apps online.
Why get rid of NPAPI? As Google's Justin Schuh explains, it's a rickety system responsible for a majority of "hangs, crashes, security incidents, and code complexity", at least as far as Chrome is concerned. According to Google's numbers from last year, Unity is the second-most popular NPAPI-based plugin, weighing at 9.1 per cent. Silverlight was number one, likely because of Netflix.
So, how has Unity responded? The editor has a WebGL export function, but the response from developers regarding its stability, performance and size isn't positive. I'm sure Unity will iron out the problems in time, but that's of little comfort to games and studios affected now.