If you don’t know the difference between hybrid and RN, I recommend reading this article, which I think is a pretty good article
See a technical point today to classify the pan-client
including
1. Small programs and quick applications
2.hybrid
3.react
4.flutter
5 electron
I don’t think that’s what I know. All the applets I know belong to the hybrid architecture of applets. To be more precise
It is ok to say that the small program is a transitional band product of RN (Weex Fast Application (Android))
However, this product shines because of wechat, not because of the excellent technology and experience, but because the product form is accepted by the public
The experience is not so bad, so you, convenient for everyone, we are also convenient, especially in the face of tens of millions of developers, the technical environment is very simple
Third party developers were happy. It’s not that different from writing HTML, but it’s a lot better than HTML. Of course, it would be nice if a vendor supports development in vscode, there is no need to develop the developer tools in NW or electron.
So how does a small program work?
Through JSbrige, he realized the native part view (component ability from the front-end perspective, actually native local view drawing ability) and system ability on the upper layer of WebView
To tell you the truth, I’ve never developed electron and flutter just a scratch
Electron and Flutter are cross-platform and cross-platform implementations of app making
A electron is based on Node and Chromium architecture implementation of multi-webView multi-process application development good products are few there is nothing to ridicule
Stolen picture
(Electron’s architecture)
Flutter develops a unique UI rendering layer based on Dart at the system layer, but it can’t be hot updated only to solve the cross-platform problem
I’m not going to pick it from the front end but from the client side it can improve the human efficiency and meet the needs
The question that occurs to me is will Dart eventually replace JavaScript…
When choosing a client framework, I think there are a few things that are important
1. How do you do
2. Debug 4 points
3. Performance 3 points
4. Single test 2 points
4. 5. Smart refrigerator