flutter:
Flutter is Google's mobile UI framework, which can quickly build high-quality native user interfaces on IOS and Android. Flutter can work with existing code and is open source and free
Flutter is used to create a high-performance, cross-platform mobile application framework, optimized for current and future mobile devices, focusing on Android and IOS low-latency input and high frame rate
The design of Flutter is very similar to react native, but it is further than RN
The development language of Flutter is Dart
The difference between flutter and RN:
1. Performance:
Since Flutter is based on the Dart language, it avoids the inefficiency of RN's communication with Javascript through a bridge, so it is better than RN in terms of performance and will be closer to the native experience.
2. In terms of learning costs:
Flutter is based on the Dart language. Relatively speaking, the learning cost is relatively high due to the need to learn a new development language, while RN is developed in JS language and based on React, which is more friendly to front-end engineers.
3. UI style:
Flutter adopts a more thorough solution to achieve cross-platform, because it implements a set of UI framework based on canvas itself, so the compatibility is better, and RN still encounters more problems in style, and it will be a bit difficult to solve trouble.
4. Aspects of maturity:
React Native was released in 2015. After more than 3 years of development, it has become relatively mature, although it is still not perfect, but the release preview version of Flutter was only launched in June this year, and the community has just developed. There are two more on github Thousands of open issues, so flutter needs more time
The same points between flutter and RN:
1. All are mobile development cross-platform solutions
2. The interface is written with a responsive view, maintaining a state machine, and only updating the interface of the smallest area changed
3. Both support hot reload, which is very convenient for development and debugging
4. Calling the service of the system still needs to encapsulate the interface, and still needs to understand native development