Construct 3 NW.js desktop app

  • Updated the original post with new downloads based on Chrome 78 (NW.js 0.42.0).

    Note: local file/folder saves are experimentally supported in the Chrome browser. Once that moves from experimental to enabled by default, there will no longer be enough unique features to justify the desktop downloads, so they will be retired. This will probably happen next year. I'd recommend switching to the browser version already if possible - see the linked thread for information on using local project files/folders in Chrome.

  • Updated the original post with new downloads based on Chrome 78 (NW.js 0.42.0).

    Note: local file/folder saves are experimentally supported in the Chrome browser. Once that moves from experimental to enabled by default, there will no longer be enough unique features to justify the desktop downloads, so they will be retired. This will probably happen next year. I'd recommend switching to the browser version already if possible - see the linked thread for information on using local project files/folders in Chrome.

    TBH, the PWA version is just as awesome!

  • Updated the original post with new downloads based on Chrome 79 (NW.js 0.43.1).

    Note: local file/folder saves are experimentally supported in the Chrome browser. With this there are no longer be enough unique features to justify the desktop downloads, so they will be retired early next year. I'd recommend switching to the browser version already if possible - see the linked thread for information on using local project files/folders in Chrome.

  • Hello Ashley,

    However, memory usage and performance remain better with the desktop version, doesn't that justify being able to continue using it?

  • Most systems have 2-4 GB of memory. A difference of 50-100mb isn't much really. It could come from browser extensions in Chrome which you could remove or disable if you really want to save 3-5% of system memory.

  • Thanks for your eternal attention Ashley but really sorry to have to tell you this again: the desktop standalone version is faster and more comfortable.

    I have the same difference in memory usage without extensions (I only used 2 that had no impact), so we are closer to 50-70% difference than 3-5% and I haven't even tried with heavy and demanding projects yet.

    Will the standalone version continue to work after this new change of direction? Does it require as much maintenance on your side (I thought it was just embedded in Chromium or something like that)?

  • Agree with Sebastien there. For some unknown reason to me, Desktop definitely works better than in browser.

  • I can't think of any technical reason it would work differently. The desktop download uses the same browser engine as Chrome.

  • Chrome also uses seperate processes for each tab, so if you have chrome open with a ton of tabs and or extensions then your chrome process will be using more resources... I have see no difference between the two and I have a pretty crappy computer.

  • I had been using the desktop build to run previews that can parse local files through nwjs without exporting the project (or importing the data to be parsed as a project file).

    My understanding is that the local file/folder save functionality doesn't really help in this situation. Are there any plans for the browser version to allow previews to access the local file system? Or, are there any other approaches besides having to either import my data as a project file each time or exporting to nwjs every time I make a change?

  • oosyrag Ashley came up with a way to use NWJS previewing here: construct.net/en/forum/construct-3/general-discussion-7/experimental-local-file-147071/page-2

    what do you think of that approach? Do you think it's an improvement because we can download NWJS at any time ourselves?

    It saves Ashley time if he no longer has to support both browser and desktop releases (I don't think he could figure out how to make the desktop app update automatically).

  • Ok, I could read the "experimental local file" post (thanks for the link alspal), this is however limited compared to NW.js (by the way, I didn't know that desktop maintenance was so heavy but I am now aware of that). It is also indicated (just 10 days ago) that desktop builds would no longer have support "in the long term", so it seems a bit early to start removing download links as early as 2020, isn't it?

    umarfarooq: Did you activate the different hardware acceleration options in Chrome settings and flags? This changed the game on my side, I had completely forgotten to have disabled them to solve crashes on another webapp several months ago (my fault, sorry). Now I'm much closer to desktop performance even if it's slightly slower (no other tab or Chrome extension are used piranha305, but it's good, it works pretty well, even very well - out of this greedy 50-70% memory usage difference).

    oosyrag, alspal

    For files in Chrome, NW.js will indeed be missing a lot, despite the beginning of a solution in the other post while awaiting clear improvements, this is IMHO a cumbersome process.

    Regarding other solutions: Changing CORS settings in Chrome does not reassure me at all for security, especially if I have to navigate when Construct is open (ok, I still don't like the idea of sharing my browser or to use a browser when working with such a powerful application, but I have to accept it or I will end up sinking in utter dismay and despair ^_^).

    When I develop, design or test, and without wanting to repeat myself, I like to automatically load files, images, animations, data, tilemaps, audio, etc. and all changes on the fly, without having to import everything by hand each time, which makes me save more than considerable time and comfort (while also avoiding tendonitis and other holy "special" moments).

    As an alternative and after a few tests, I load these asset sources via a local web server (WampServer), it works well even if this adds additional constraints in the work organization. Fortunately, I don't need to install an SSL certificate for the moment and the basic HTTP protocol seems to be enough (sweat).

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Amazing. Good job guys!

  • It would be nice if this worked offline without needing an internet connection. I tried it offline and got the error message:

    Jason

  • It should do already. It looks like you're using the Windows Store version, try the NW.js version instead.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)