Browser Plugins vs Extensions – the difference
One of the least understood concepts in the Browser Plugin world is — browser plugins. What they are, and even more: what they are not. Probably at least once a week I answer a question somewhere on a forum or on the comments on this blog and say “You can’t do that with a plugin; you need an extension”.
Many people confuse plugins and extensions in the browser world. They sound like they should be the same thing, but in fact they are very different.
What you can do with a plugin
Examples of common plugins include:
- Macromedia Flash
- Microsoft Silverlight
- Apple Quicktime
- Adobe Reader (at least this includes a plugin in addition to the rest of the application)
Some plugins respond to a mime type and can run in place of the page, such as Adobe Reader, which allows you to view PDF files in your web browser. Again, however, it affects only that page, and no others. In Firefox, Chrome, Opera, and Safari, these plugins are usually called “NPAPI plugins”, since they are written using the NPAPI. In Safari, you could also use a Webkit Plugin. In Internet Explorer you would do this with an ActiveX Control.
What a plugin cannot do
Plugins have to either handle a mime type or be embedded into a web page. They don’t get put there automatically. They don’t create toolbars. They don’t affect browser menus. They don’t know about tabs, or even about other pages in the same browser process. They don’t make coffee, tea, or hot chocolate, though they could be written to control an external appliance to do so if you really wanted. They don’t automatically process the content of every web page loaded.
“But wait!” I hear you all cry. “We have seen these magical things done! (well, except the hot chocolate machine)”
“Yes,” I reply. “Those are extensions.”
Extensions, or “add-ons”, can often do these magical things. They can add onto the browser UI, process pages that the browser loads. They do all sorts of things. However, they are not the same thing as plugins; they affect the web browser itself, not really the page. They may affect a page as well, of course. In fact, you can even put a plugin inside an extension, at least in Firefox. However, if you write an extension for Firefox, you’ll probably have to write it again for Chrome, Safari, and IE… one for each. Perhaps there is a framework out there for writing portable extensions, though. It’s not really my area of expertise, so I don’t know.
Examples of extensions / add-ons:
- DownThemAll for Firefox
- Firebug for Firefox
- Google Voice extension for Chrome
- Let there be Comic Sans for Safari
An extension could contain a plugin, but a plugin can’t contain an extension
One very common way to install a plugin in Firefox is to use a .xpi file. This is an extension. It may have a NPAPI plugin inside of it, but it is still an extension. It will not work on other web browsers, even though your NPAPI plugin may work perfectly fine on Chrome and Safari if installed in another way.
Conversely, a plugin by nature does not include an extension.
Nearly a year ago now I began a project called FireBreath, which is a cross-platform browser plugin architecture. FireBreath is, frankly, awesome. You can literally get a plugin up and going in under 10 minutes if you already have everything installed. That means you can spend your time doing other more important things, like actually developing your functionality, rather than spending all your time figuring out how to deal with the plugin APIs.
That said, FireBreath is a cross-platform browser PLUGIN framework. It does not create extensions. It will never be able to create extensions. If you need an extension, you need something else.
When not to use a plugin
Finally, and this is a topic that people seem to think is a little strange coming from me, there are many cases when it is not a good idea to use a browser plugin. In fact, a good rule of thumb is that if you can do what you need to do without one, don’t use one.
- There are no really good ways to install browser plugins that will work 100% of the time
- XPI install only works on one profile in firefox
- CAB install only works in Internet Explorer and is sometimes a little unreliable
- ClickOnce works only in Windows and only if .Net is installed
- Java installers only work reliably and consistently on Mac OS
- MSI or EXE installers while being the best method IMHO require a little more work on the part of the user, and the average user is… less savvy than you are, shall we say.
- Plugins have to take into account a large range of hardware types
- If you use graphics libraries such as OpenGL or DirectX keep in mind that every graphics card works a little differently with these technologies. You will run into weird cases where your plugin doesn’t work on someone’s computer. If your luck is like mine, that computer will belong to an executive at a fortune 500 company (yes, that happened to me. no, it wasn’t fun)
- Plugins don’t work until they have been installed
- This is a major limiting factor to uptake of your site. Many users don’t want to install yet another plugin on their machine, and many get lost in the incredibly complicated task of downloading and running the installer.
If all of those things haven’t convinced you that what you want isn’t actually a browser plugin — great! That’s why I’m still posting about this stuff. Despite all the reasons not to use a plugin, there are also a lot of cases where it’s a good idea. Browesr plugin development can be a lot of fun! Good luck!