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)

Creating a Chat System with Electron and React – Enhancement, Testing, and Delivery

We finished the last chapter with a static prototype. We learned about React, composed the components, but didn't provide them with any state. Now, we will start binding the state of the application window to the Header component. As the state concept clarified, we will move to the chat services. After getting a brief introduction to the WebSockets technology, we will implement both the server and client. We will bind the service events to the application state. Finally, we will have a fully working chat. We won't stop on it, but will take care of the technical debt. So, we will set up the Jest testing framework and unit-test both the stateless and stateful components. Afterward, we will package the application and publish releases though a basic HTTP server. We will extend the...