Book Image

Cross-platform Desktop Application Development: Electron, Node, NW.js, and React

By : Dmitry Sheiko
Book Image

Cross-platform Desktop Application Development: Electron, Node, NW.js, and React

By: Dmitry Sheiko

Overview of this book

Building and maintaining cross-platform desktop applications with native languages isn’t a trivial task. Since it’s hard to simulate on a foreign platform, packaging and distribution can be quite platform-specific and testing cross-platform apps is pretty complicated.In such scenarios, web technologies such as HTML5 and JavaScript can be your lifesaver. HTML5 desktop applications can be distributed across different platforms (Window, MacOS, and Linux) without any modifications to the code. The book starts with a walk-through on building a simple file explorer from scratch powered by NW.JS. So you will practice the most exciting features of bleeding edge CSS and JavaScript. In addition you will learn to use the desktop environment integration API, source code protection, packaging, and auto-updating with NW.JS. As the second application you will build a chat-system example implemented with Electron and React. While developing the chat app, you will get Photonkit. Next, you will create a screen capturer with NW.JS, React, and Redux. Finally, you will examine an RSS-reader built with TypeScript, React, Redux, and Electron. Generic UI components will be reused from the React MDL library. By the end of the book, you will have built four desktop apps. You will have covered everything from planning, designing, and development to the enhancement, testing, and delivery of these apps.
Table of Contents (9 chapters)

React

React is gaining momentum. It is the most trending technology, according to the 2016 Stack Overflow developer survey (http://stackoverflow.com/insights/survey/2016#technology). It is interesting to note that React is not even a framework. It's a JavaScript library for building user interfaces--very clean, concise, and powerful. The library implements the component-driven architecture. So, we create components (reusable, composable, and stateful units of UI) and then use them like Lego blocks to construct the intended UI. React treats the derived structure as an in-memory DOM representation (virtual DOM). As we bind it to the real DOM, React keeps both in sync, meaning that whenever any of its components change their states, React immediately reflects the view changes in the DOM.

Besides that, we can convert virtual DOM in the HTML string (http://bit.ly/2oVsjVn) on the...