Many readers left their thoughts and thoughts on the previous two Flutter articles compared to iOS Native and React Native respectively. However, some readers sent in different sounds, focusing on the size and smoothness of the Flutter installation package. I took the time to take a test, and here are my results.
Installation Package Size
Some readers pointed out that the release package they finished was only 6~7MB, which was very different from the data I provided, and that I used debug instead of release for comparison.
At first, I was also very strange. After repeatedly confirming that my package was release, I tried to think about other directions. My previous installation package data was released directly to the App Store and compiled through the App Store cloud.
It looks like the deviation was found, but why is the size of the cloud-compiled package so different from the local package? When I tested native apps again, I found that there was little difference in the size of the native and the cloud-compiled packages.
Could the contents of the package be different because Flutter is packaged differently? I tried unpacking the two ipAs separately and found that there was no difference in the contents of the packages and that the two packages were of exactly the same size.
The conclusion might be that the compression ratio is different between the two packages, right? However, there is one thing that can be confirmed, no matter what packaging method, finally installed on the mobile phone disk size is the same, is 30MB+. Therefore, the result I got explained the doubts of some netizens, and also confirmed that my previous analysis and judgment on the application of Flutter was ok.
Another point to note is that the tests I’ve done so far have been based on iOS, not Android. According to tests sent in by users, the android installation package is significantly smaller than the iOS installation package. This is because part of the Flutter framework is built into Android itself, and Fuchsia will definitely build the Flutter SDK directly into the system, which will make the gap even bigger.
fluency
As for the fluency, many users felt that the fluency of the Flutter was not as bad as my test results and that I also used Debug mode for the test. Since fluency sensitivity varies from person to person, I provided my own subjective feelings along with Xcode’s framerate chart. In addition, I uploaded the original and the Flutter project to the App Store and GitHub, where you can easily download it to your own devices.
But I have to make my point: At least for now, The fluidity of Flutter on iOS is not quite as good as the iOS native app, nor is it quite as smooth as the 60 frames it claims to be.
Feel free to leave a comment below if you have any questions.