Last weekend there were a couple of great conferences in Italy. My colleague Alessandro was busy at the #Pragma Conference, while Emanuele took a great talk about the technologies we used to build Spreaker Studio for Desktop app at the Node.JS conf.
The app, that will be officially launched next Wednesday (in just 2 days), has been built upon Electron + React.js + our proprietary native audio processing library we currently use on Android / Windows / OSX (iOS app has a different implementation).
The following slides give you a sneak peek of the foundation, how Electron works, why it works for us, pros and cons. It’s a definitely suggested read, either you’re planning to build a desktop app or just curios about the technology behind it.
- Build a desktop app playing with HTML, JS and CSS out of the sandbox
- The two main technologies available: Electron and NW.js
- “NW.js lets you call all Node.js modules directly from DOM and enables a new way of writing applications with all Web technologies. It was previously known as node-webkit project.“ - NW.js website
- Our choice was Electron:
npm install -g electron
- Basically you are writing a client app: ReactJS, SystemJS, JSPM, Babel, other libs (moment, underscore, emojione, url, reconﬁg, analytics, …). This is very interesting given the state of modern frontend tools.
- You can debug with chromium tools
- You can leverage desktop integration: Menu, Notiﬁcations, Shortcuts, Multiple displays
- You can go down a bit RPC server to expose app API using raw sockets
- You can get more from chromium via command line switches
- You can start digging “into the rabbit hole” - Electron is moving faaaast, use NaN to write add-ons
- You can unit test inside the electron environment
- You have autoupdates out of the box (works only with signed app, works in a different way on windows) - single script on a server returning update zip uri and metadata
- Crash reports are super easy to collect and test! Every native crash (out of memory, segmentation faults) electron send a POST to conﬁgured
submitUrlwith: platform informations memory dump in minidump at not so easy to decode :) For each version you deliver you need to get electron debug symbols from project release page. Generate symbols for your native libs with breakpad tool dump_syms. Put them in a er (with a standard structure) and use minidump_stackwalk to symbolize them in a correct way. You can build these tools from break pad source tree
- You can add branding and package your app for mac and windows in a breeze (see electron installer, electron packager)
- You can distribute your code in a “safe way”. Inside electron you can treat your asar bundle as a normal directory. (you may want to uglify/obfuscate your code)
- All these things makes me very happy!
- Sadly electron has some downsides: you are bundling Chromium with every update, compressed app size is around 40MB, you can’t hit Mac App Store and Windows Marketplace, sometimes you have to dig into source code (this can be fun) and spend time on github project issue tracker
- but… it works for us… makes desktop development fun… makes desktop development fast.
You may also be interested in ...
- Electron - Slow performances in background
- Electron - Open DevTools in a popup
- Electron - Enable copy and paste
- Electron - Signing a Mac Application
|Incontro DevOps 2020||Virtual||22 October 2020|