Another thing, it enables us to rapidly iterate and deploy through one code base. Maintaining code bases for multiple platforms will be like a ball and chain on our feet. End user will get a better product.
Apps wrapped in a browser are blatantly clunky and feel out of place from the OS compared to something using native controls, not to mention consuming more resources and battery. [0]
What specific parts of Construct 3 do you feel are clunky?
Menus, panels, windows, controls, fonts, fullscreen support, accessibility..too many to list, and WHY do I get the ugly red X button on the right corner when I'm on a Mac?? Why do you force me to use Windows UI paradigms, after making such a big deal about web apps = yay portability?
The reality remains that for now and the foreseeable future: Users do NOT, CAN not, get the best possible experience unless you're willing to write and maintain native apps.
Well, you're kinda making a point for me there. Why would a game developer use a Chromebook or an Android device?
The second point applies more or less to an Electron app, too.
Because they are usually a lot cheaper and more accessible worldwide.
As an example, a market we've identified is educational in US, there's millions of Chromebooks out there gathering dust. If you are an educational user, this could open a lot of doors.
> The second point applies more or less to an Electron app, too.
Yes, we are planning on distributing desktop builds via Electron. First phase is in browser only as there's a little bit more to prepare before we can release downloadable builds. Is that what you mean?