Are plugins really going away?

Yes. Plugin-less communications are the only viable vision for browser-based communications going forward. Support for browser plugins is waning due to ongoing security & compatibility concerns. For example, Google & Mozilla are terminating support for the Netscape Plugin API and plugins in 2014[i] [ii]. For Internet Explorer 10 and 11, Microsoft has issued a statement of direction without plugins. In turn, plugin warnings will appear with every use unless in "enterprise mode" or "desktop mode".  This points to a transition period to migrate Internet Explorer users off of plugins for future versions of Internet Explorer[iii]. In addition, plug-ins are not allowed on Chromebooks.

Today, Google Chrome, Mozilla Firefox and Opera all support real-time communications without a browser plugin. These three WebRTC browsers correlate to 1.2 billion endpoints today and by other estimates 63% of the browser market (via pageview market share at StatCounter) ...and growing.

With broadening support by Google, Microsoft and Mozilla, the W3C has commenced defining ORTC (Object Real Time Communications) as an extension and simplification of WebRTC. ORTC solutions are plugin-less and hide codec complexities from web & JavaScript developers. Microsoft has an early implementation of ORTC today. As we continue to innovate, CaféX products will be one of the first to implement plugin-less ORTC support.


[i]       Lucian Constantin, “Google Chrome to block and banish plugins built using popular NPAPI architecture”, PC World, September 24, 2013 (

[ii]       Zach Walton, “Firefox To Soon Block Plugins By Default”, WebProNews, September 25, 2013 (

[iii]      Internet Explorer Dev Center, “Get ready for plug-in free browsing” Microsoft Corporation (








Comments are disabled on these articles if you require help contact

Have more questions? Submit a request