What is React Desktop and what are its top alternatives?
Top Alternatives to React Desktop
React Native Desktop
Build OS X desktop apps using React Native.
The fastest way to build beautiful Electron apps using simple HTML and CSS. Underneath it all is Electron. Originally built for GitHub's Atom text editor, Electron is the easiest way to build cross-platform desktop applications. ...
Create native desktop applications through a React syntax, on all platforms
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...
It is a set of graphics and media packages that enables developers to design, create, test, debug, and deploy rich client applications that operate consistently across diverse platforms. ...
It is a full development framework with tools designed to streamline the creation of applications and user interfaces for desktop, embedded, and mobile platforms. ...
Element is a Vue 2.0 based component library for developers, designers and product managers, with a set of design resources. ...
React Desktop alternatives & related posts
- Easy to make rich cross platform desktop applications61
- Open source45
- Great looking apps such as Slack and Visual Studio Code10
- Because it's cross platform4
- Use Node.js in the Main Process3
- Uses a lot of memory13
- User experience never as good as a native app7
- Does not native4
- No proper documentation3
related Electron posts
Slack's new desktop application was launched for macOS. It was built using Electron for a faster, frameless look with a host of background improvements for a superior Slack experience. Instead of adopting a complete-in-box approach taken by other apps, Slack prefers a hybrid approach where some of the assets are loaded as part of the app, while others are made available remotely. Slack's original desktop app was written using the MacGap v1 framework using WebView to host web content within the native app frame. But it was difficult to upgrade with new features only available to Apple's WKWebView and moving to this view called for a total application rewrite.
Electron brings together Chromium's rendering engine with the Node.js runtime and module system. The new desktop app is now based on an ES6 + async/await React application is currently being moved gradually to TypeScript. Electron functions on Chromium's multi-process model, with each Slack team signed into a separate process and memory space. It also helps prevent remote content to directly access desktop features using a feature called WebView Element which creates a fresh Chromium renderer process and assigns rendering of content for its hosting renderer. Additional security can be ensured by preventing Node.js modules from leaking into the API surface and watching out for APIs with file paths. Communication between processes on Electron is carried out via electron-remote, a pared-down, zippy version of Electron's remote module, which makes implementing the web apps UI much easier.
The Slack desktop app was originally written us the MacGap framework, which used Apple’s WebView to host web content inside of a native app frame. As this approach continued to present product limitations, Slack decided to migrate the desktop app to Electron. Electron is a platform that combines the rendering engine from Chromium and the Node.js runtime and module system. The desktop app is written as a modern ES6 + async/await React application.
For the desktop app, Slack takes a hybrid approach, wherein some of the assets ship as part of the app, but most of their assets and code are loaded remotely.
- Pretty awesome1
related React Native Desktop posts
related Photon posts
- Very fast3
- Full cross plataform2
- React style1
- Is native1
- Code reuse with react native apps0
- Low community for the moment0
related Proton Native posts
- Virtual dom646
- Data flow171
- Isn't an mvc framework122
- Reactive updates112
- Explicit app state109
- Learn once, write everywhere21
- Uni-directional data flow17
- Easy to Use16
- Works great with Flux Architecture14
- Great perfomance9
- Built by Facebook6
- Feels like the 90s4
- TypeScript support3
- Easy to start3
- Server side views3
- Fast evolving2
- Great migration pathway for older systems2
- Simple, easy to reason about and makes you productive2
- Fancy third party tools2
- Excellent Documentation2
- Scales super well2
- Just the View of MVC2
- Server Side Rendering2
- Rich ecosystem2
- Split your UI into components with one true state1
- Every decision architecture wise makes sense1
- Super easy1
- Beautiful and Neat Component Management1
- Has functional components1
- Very gentle learning curve1
- Strong Community1
- Has arrow functions1
- Allows creating single page applications1
- Start simple0
- Requires discipline to keep architecture organized31
- No predefined way to structure your app19
- Need to be familiar with lots of third party packages18
- Not enterprise friendly6
- State consistency with backend neglected1
- One-way binding only1
related React posts
I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.
It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.
- Community support less than qt1