Why use Flutter

  • Excellent cross-platform capabilitiesFlutter development is not limited to mobile cross-platform. Flutter supports Web development, back-end development, PC desktop application development, and embedded development
  • Good performanceThe experience and smoothness of flutter development app is basically the same as the native experience, with almost no lag felt
  • Reliable ecologyFlutter was developed and maintained by Google, and has been released frequently. The community ecosystem of Flutter is now approaching perfection
  • Excellent two-end consistency: The performance of both ends of flutter is much more consistent than that of RN and WEEX in TERMS of UI. Designers only need to focus on one end of the design, saving design manpower

How to carry out flutter modification

1. Try small

  • Since this is the first attempt to retrofit FLUTTER of the company’s project, for the sake of product stability, marginal businesses were selected for a small trial.
  • The plan is to embed both ends of the Flutter Module (iOS and Android)

Why use the Flutter Module: The Flutter Module is less intrusive to the original project and can ensure that small changes made before will not affect product iterations

2. Build the underlying flutter ecological components within the underlying company

  • After step 1 has been tried, start building the company’s underlying FLUTTER ecological components
  • First, size adaptation, log management, loading animation and other basic components
  • Then there are network libraries, JSON parsing, routing and other general components
  • Finally, there are business components such as photo taking/picture picking, business plug-ins, self-developed packages, custom message channels, and so on

3. Go back and transform the original original module

  • After the modification is completed in Step 2, break down some module components that need to be modified for flutter modification
  • In this step, the whole project of Flutter is gradually improved, based on the original, as a framework, to replace each business using Flutter.
  • Not everything, of course. It depends on whether the business is suitable for transformation, and consider product stability and labor costs

4. Optimize the performance of existing FLUTTER modules

  • By this time, the basics of the Flutter embed native project were beginning to take shape
  • The next step is to optimize those modules that are not performing well enough

The new project

  • For new corporate client projects, in principle new Flutter projects should be directly created without a particularly strong native base as a development condition, rather than using native projects as a framework base