The introduction docs also claim "In Electron and NWjs, you have to install Node.js and hundreds of dependency libraries. Embedded Chromium and Node make simple apps bloaty. Neutralinojs offers a lightweight and portable SDK which is an alternative for Electron and NW.js."
Yet the installation here starts with NPM and depends on Node.
Sorry, but I don't see a significant difference between this and Electron just from the comparison chart linked in the docs. https://github.com/Elanis/web-to-desktop-framework-compariso...
Save for the fact that Neutralinojs is not listed as having any support for automated testing where Electron does.
The data there shows smaller and faster builds on empty apps but that doesn't count for much since no one ships empty apps.
Needs a fair comparison against its claimed competitors using app examples that at least mimic real world apps. For example, if building the typical kind of application people would build in Electron still results in a smaller deliverable and much faster build, that would start to make a case for a better developer experience.
Though I would guess that most developers would not switch and learn a new framework just to get slightly faster builds before considering test time. Integration test run times tend to take up most of the time in any build process.