They also offer custom APIs that bring the following advantages:
Sounds great? Then let’s get started. In this article, we’ll become familiar with NW.js in practice and learn how to create a hybrid application. An example application that was built using the instructions from this article can be found on GitHub.
First, there’s one thing to mention: NW.js isn’t the only framework for hybrid apps. There’s another competitor called Electron. It started in 2013, two years after NW.js, but because it’s from GitHub it quickly became well known. Now you might be interested in the differences between them. Here are the advantages of NW.js compared to Electron:
chrome.*APIs. These APIs can be used to interact with the browser. (You can find more information about this in the NW.js docs.)
nwjctool, your code will be compiled to native code. (See this article for more information.)
However, Electron also has some advantages worth mentioning:
There’s also a fundamental difference. NW.js applications specify their entry point in the form of an HTML file. This HTML file will be opened in the GUI directly.
Note: If you really prefer the advantages of Electron, check out SitePoint’s recent article on creating desktop apps with Electron.
Copy and paste this URL into your WordPress site to embed
Copy and paste this code into your site to embed