Like any platform NW.js has some bugs but usually they get fixed in updates. And if you stay on the same version, nothing actually changes so it shouldn't suddenly break overnight. Are there any active issues with the latest NW.js version?
I'd point out the new Windows WebView2 exporter is just ~650kb for a zipped empty project - even smaller than GameMaker. Also the cross-platform inconsistencies were about whether things work the same across platforms - JS may have its quirks, but at least they're exactly the same on all platforms so they don't become porting hurdles.
Relying on third-parties is basically unavoidable with modern software, as I mentioned in this comment.
We recently introduced the new Windows WebView2 and macOS WKWebView export options providing lightweight alternatives for desktop publishing - particularly relevant to people who had complained about the size of NW.js in the past. As for consoles, it's difficult for us to act on that unless console makers add support for HTML5 games - but there are third-party porting services out there.
Using third-party software is simply unavoidable with modern software development. Changing technologies still won't completely solve that. For example with native engines graphics driver issues can be far more problematic - and graphics card vendors are almost impossible to communicate with. If there's a public bug tracker, at least there's a viable route to getting something fixed - and we routinely do file issues on behalf of user issues and follow them up. Lots of bugs do get fixed this way. Some might slip through the cracks but as ever, changing technology is not a silver bullet that will solve everything.
What's actually wrong with using third-party tools? No technology is perfect, everything has its quirks, but in general they work out great. And if there's no significant downsides, it's a great way to speed up development. With tools like Cordova, you're still getting much faster performance with JavaScript, so there are big wins too. And Construct provides services like the mobile app build service that help make it easier to publish to Android without needing to install and configure loads of developer SDKs.
Edit: I'd add the whole reason JavaScript has so many benefits, is because we rely on third parties to provide the programming language. The point of the post is that if we made our own programming language it would likely have several major pitfalls. So there's big upsides to relying on third-party tools too.
The blog post includes both a JavaScript and event block based version of the performance benchmark. You can try them both out yourself.
The plugin is fully documented, including with setup instructions in the Mobile Advert manual entry. Please note however the instructions will shortly be updated for the latest SDK updates.
If your project opens but doesn't run please file an issue: https://github.com/Scirra/Construct-3-bugs
Construct 2 was retired in July and will no longer be updated or supported at all.
IIRC there have been no changes to Android App Bundle builds in this release. It should be working exactly as it did before.
Try using the Shift+F5 keyboard shortcut to debug the current layout.
See Using 3D in Construct!
The function object was replaced with built-in functions around 2 years ago.
Based on that forum thread, it might just be because you used the unstable Canary webview.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.