To help developers who rely on browser Plug-ins to invoke Third-party programs, Google has added a new feature in Chrome-native communication (Native messaging) interface. This interface will come with chrome 291 for Windows, Linux, and OS X. Since January, Google has been phasing out support for NPAPI, and plug-ins that rely on Third-party software to enhance browser capabilities have been the hardest hit.
The "Native Messaging" interface is introduced in Chrome 29, so programmers don't need plug-ins to invoke third party software.
Google will temporarily allow several of the top Plug-in to continue to exist, but after that, everyone needs to find ways to adapt to the new solutions. Google and Adobe, for example, will be dedicated to flash functionality built directly into the new Interface (PPAPI).
Google wants to completely remove Chrome's support for NPAPI by the end of 2014, but the exact time will still depend on usage and user feedback. As for the "dry" npapi reasons, Google said:
"Today's browsers are faster, safer, and more capable than their ancestors." This means that Npapi, the 90-generation architecture, has become a major cause of ' hanging ' (hangs), crashes, security incidents, and code complexity.
Google also mentions that NPAPI does not support mobile devices, which is a big trend in the world. In addition, Mozilla also plans to ban the Npapi plug-in in 2013 of December.