Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing NW.js (w/xvfb) vs Xojo, the Slant community recommends NW.js (w/xvfb) for most people. In the question“What are the best tools for building cross-platform desktop apps with web technologies?” NW.js (w/xvfb) is ranked 2nd while Xojo is ranked 8th. The most important reason people chose NW.js (w/xvfb) is:
The integration of Node with the DOM in NW.js opens up a number of new options in how your headless testing workflow can be facilitated. The distinct separation of JavaScript contexts, the introduction of a separate node context, and the ability to cross communicate, offers a lot of power and flexibility.
Specs
Question Ranking
Pros
Pro Node integration
The integration of Node with the DOM in NW.js opens up a number of new options in how your headless testing workflow can be facilitated.
The distinct separation of JavaScript contexts, the introduction of a separate node context, and the ability to cross communicate, offers a lot of power and flexibility.
Pro NaCl support/integration
Access to the Native Client offers up more options in implementing your testing workflow.
Pro Easy to use
Easy to make compiled native apps.
Cons
Con xvfb Requirement (for now)
Headless is on the NW.js roadmap, but for now xvfb is necessary to get going. The community has done the work and you can find the details here.
Con Subscription-based/Not free
Using this product you're betting the company will still be around. If they get bought out by an enterprise that wants to use the tech internally, all they need to do is stop offering subscriptions and suddenly you're scrambling to rebuild your entire app on other technology.
Con No Android support
They plan to eventually support Android, but for now, they only support iOS.
