Construct 3 NW.js desktop app [Deprecated]

Where can I get the NW.js version? I cannot find a download link anywhere.

It’s in the first post on page 1.

I have seen a few others post this same question but looking for some update on being able to use Construct 3 with file/folders and not a single c3p file. We have several developers primarily using Mac's which mean we cannot use the desktop version. Installing as a PWA cuts down the step of going to the browser but doesn't support saving the project locally in a reasonable way that would allow us to easily work with source control. It is also not possible to expand the c3p file out to files/directories which is much more preferable for version control.

Are there any other options out there or is Construct 3 going to continue to be primarily a single developer tool or require a windows machine for any team level development?

Thanks

Local file & folder saves in Chrome have been supported for some time on all platforms. It's now enabled by default in beta releases as of r183.

I've been planning how we might approach the effective retirement of the desktop builds. With this plan, we won't actually really fully retire them: instead we will stop distributing builds ourselves (allowing direct downloads from nwjs.io instead), and gradually unify the codebase with the browser version.

Currently the plan is:

• Instead of providing our own desktop downloads, we will just provide the package.json file which you can add to any NW.js download.
• Replace most NW.js code with the same code as is currently used in Chrome. For example this means deleting all the NW.js-specific saving code, and replacing it with the local file & folder saves as used in Chrome (but ideally without permission prompts).
• The Windows Store download will be fully retired. Users will be advised to switch to either the Chrome or NW.js version.

This means:

• We no longer have to manage NW.js releases ourselves, freeing up our time.
• You can download any NW.js version yourself, without having to wait for us to release it. This also includes using NW.js on other OSs that we didn't previously provide builds for (e.g. macOS, Linux).
• We can delete the vast majority of NW.js-specific code and stop having to maintain it with bug fixes and such.
• You can still preview and debug with NW.js features using the editor in NW.js.
• It's largely backwards-compatible: everyone who has already downloaded the NW.js desktop download can keep using the editor with that.

Basically this turns the NW.js version of the editor in to the same thing as you get in Chrome, but with NW.js features still enabled in preview mode. I think this covers everything we want, which is basically eliminating the NW.js maintenance overhead, while keeping all existing features that users rely on (like debugging with NW.js). We'll also provide the NW.js version of Remote Preview on a similar basis, so you can Remote Preview your project with NW.js features active somewhere else without having to send your full project.

Let me know if you have any feedback or if there's anything I missed. I think the next step is to formally notify users of the Windows Store app that it will be retired, so I will do that in the near feature if there are no objections.

We can delete the vast majority of NW.js-specific code and stop having to maintain it with bug fixes and such.

How significant is the mentioned code? Could it potentially corrupt projects or is it just minor stuff without any major impact?

I generally like the plan and end goal. Posts about current progress would be great.

How significant is the mentioned code? Could it potentially corrupt projects or is it just minor stuff without any major impact?

I'm not sure what scale to measure significance on, but there's lots of desktop-app specific code scattered across the editor, and most of it is now redundant as Chrome can basically do everything NW.js can now. Removing it helps simply the codebase and should reduce the number of bugs we have to deal with pertaining to that desktop-specific code too. In every case we'd just switch it over to doing what Chrome already does, so it seems unlikely any serious bugs will be introduced by doing this.

Personally I prefer the desktop version (specifically windows10) because the editor is much faster then the browser version.

I have not tried the NW.js version. Is it as fast as the desktop version?

Fair enough, I'm just glad we'll still be able to continue to directly preview with NWjs.

LuisCGForte - that looks like an old bug we fixed ages ago. Try downloading the latest version of the desktop app from the first post in this thread.

Please file a bug report following all the guidelines and we'll look in to it.

You need to follow the bug report guidelines for us to be able to help, though.