For several years, if you wanted to publish web content made in HTML/CSS/JS as a desktop app, the answer has been to use Electron or NW.Js . For us, we've long...
I see auto-updating as an issue, releasing your game on top of a moving target means it will break
File size is a complete none issue for the platform it targets
Thanks for talking about your plans for Linux and Mac, I was worried that NWjs gets dropped in favor of WV2 without having a replacement for them
Very excited about XBox
Backwards compatibility for addons is huge, it really helps trust if devs don't have to fear that they could rot away
Only thing I don't like is the auto updates. Nice for development, but for release I want to nail it all down, lock in the version I did all the testing on. But I did see that there's a fixed version too
Would be awesome if we could choose between the evergreen and fixed version
I was still a bit skeptical about WV2 because of some unanswered questions I had, but this blog addressed pretty much all of them and now I'm very excited about it, thanks
Construct content has generally worked fine for years with breakages being very rare, so I think auto-updating is a good default. (Other updates like OS updates or driver updates can always break stuff too - you should always be prepared to do some maintenance!) But if you want to ship a specific browser engine with your app, you still can with WebView2 using "fixed" mode. It's documented in this guide.
Thanks for the link, I didn't know there was already a tutorial for it. Bookmarked.
Yes it is rare but consistent that things just stop working on the web. It happened to me and only with the live browser version, while the NWjs version was still fine.
Though fixing it was easy because I still have a sub, and Construct and I are still around to update it.