Now, the fact that this technology was born in the web browser has some interesting implications. The World Wide Web is not a completely safe place. Browsers have responded by cordoning off the contents of the web from the rest of the computer, in an attempt to limit the potential danger that comes from poking around the 'Wild Wild Web'. This is a good thing, but it can make a programmers life difficult. For example, in most programming languages, it's easy to do things like read and write files, make system calls or even access hardware features. No one would want some random webpage to have that kind of access.
In the meantime, there has been a strong trend towards mobile devices. Many things people used to rely on desktop and laptop machines to do are now done on phones and tablets. For a variety of reasons, these devices have come to be very app-centric: everyone interacts with their devices through a collection of 'apps', usually downloaded from a more or less trusted source.
Formerly known as 'Phonegap', Apache Cordova provides an API (Application Programming Interface) and a way to build HTML apps to produce installable mobile apps. The key is that the Cordova API provides access to features that are not normally available to an HTML5 app, whether its device hardware like the camera and GPS, or system resources such as the file system or the contacts database. Standard Cordova came with a significant library of such API's, but as it has grown, the Cordova framework has developed from an all-in-one solution to a plugin approach. I'm not always a big fan of "plugin" architecture. There's always a trade-off between an all-in-one approach, with batteries included, and a bare-bones only what you need approach. The former is easier when you're starting out and don't need to think about a bunch of details, but the latter can be more efficient and flexible, once you're know what you're doing.
In fact, many software projects tend to follow that pattern. First they start out with everything built in, then at some point they start adding so many features they realize it's a good idea to allow plugins or modules of some sort, then they realize a lot of the things that were built-in could be done as plugins, et voila, a plugin architecture is born. Thus I initially greeted Cordova plugins with some skepticism, figuring it's just following the natural course of a software project, but now I think I was really missing the significance of the change.
The really cool part about a Cordova plugin isn't about the architecture of the Cordova project. The cool part is that it makes it really easy to add functionality to web apps that would otherwise be restricted to native apps. A great example I ran across recently is the Dolby API plugin.
Now, if you're lucky enough to have a mobile device with support for Dolby audio, you can take advantage of it in your mobile app. The audio processing technology can enhance on-device audio, offering a choice of audio profiles optimized for gaming, music, movie watching or speech. This allows a mobile app to enable and control the use of dolby audio processing built in to some devices, if present. The API uses a familiar callback based approach to enable and configure the audio processing features.
If you're using the Intel XDK to build a web app, it's really easy to add this plugin to your app and then use the API in your code. On the project page, under plugins and permissions, there's a sub-menu called "Third-Party Plugins". Choose "Get Plugin from the Web" and point it at the git repo, "
https://github.com/DolbyDev/Dolby-Audio-Plugin-for-Cordova.git", with a name of your choosing and the plugin id "
com.dolby.dax". In your app, you'll need a line like this to initiate Dolby processing:
dolby.dap.initialize(dolby.DapProfile.GAME, onDsConnected, onFail);
onDsConnected() is run if/when the Dolby feature is enabled, otherwise
onFail() is run. In place of "
GAME" you can choose "
VOICE" or "
MUSIC" to get audio optimized for different situations. If you want to try it out, I have a sample app you can import to the Intel XDK on github at https://github.com/oldgeeksguide/dolby-cordova-plugin-example.