Subtitle "Treat Flutter rationally"
Author: Nuts
Flutter is generally recommended when creating iOS and Android apps because it is easier and more efficient to use. Because of Flutter's many advantages, it is a great candidate for mobile apps in many situations. Its performance, logical architecture and documentation are highly regarded. Domestic communities are also very active, but in some cases Flutter may not be the most suitable. This is what we will see in this blog. Let's look at some scenes..
1. When your project relies on primary libraries for a specific device and platform
If your project requires a Wear OS version or Smart TV app, you will encounter some problems. You can technically build a Flutter application for these platforms. However, Wear OS does not support many of Flutter's development features. So it will cause you trouble.
For Android TV, you must use the control logic from scratch. Because Android TV only reads remote control input, while Flutter uses a touch screen and mouse to move, this is the case. It's up to you to decide which is more important.
2. When your application requires high application size
Because flutter is not native, it adds some other libraries to work on top of the application. If every byte is important to your application, you may need to develop on a native platform. Because it has built-in widgets rather than using native platform widgets, the minimum size of Flutter applications is more than 4MB, which is significantly larger than native Java (539 KB) and Kotlin (550 KB) applications.
To be honest, its competitors have the same problem, React Native takes up 7MB.
But due to advances in hardware technology, even smartphones are equipped with greater memory and storage space. So most people don't care about the size of the application.
3. hardware support
Flutter is not recommended for applications that connect to hardware devices via Bluetooth. Since it does not use the device's Bluetooth itself, some connection issues and performance issues can occur.
4. Flutter for Web
It is not html. Yes, even the web version of Flutter has been officially released, but it will not shake the Internet world. There are many simple and effective libraries on the market for developing websites. When it comes to websites, page load speeds, SEO, performance and everything that matters, Flutter has a hard time doing this with a simple dart to Js Engine.
But it is too early to judge. Flutter may come up with wonderful optimization performance. Let's stay tuned. Uncle Wang's video also explains such issues. The address is here.
Can Flutter make a website?| Flutter Web Quit Guide| It only takes a few minutes from getting started to giving up
5. Platform-specific look and design
Material Widgets and Cupertino widgets are two different building blocks of Android and iOS applications, respectively. You could use both widgets when creating the Flutter app, but when we built and used the Material widget for iOS, the app lacked a native look and feel. To achieve a native look for both applications, we should examine the platform in the code and render specific widgets, which are the worst performing parts of the coding and application.
6. Lack of third-party integration
Although Flutter has 19k + libraries and plug-ins, it still lacks many popular libraries and SDKs. Many packages are currently being developed and migrated to Flutter. If you are developing an application that relies mainly on third-party plug-ins, check that the latest version of the SDK is suitable for Flutter. As for how to check,
In addition, always prefer actively maintained repositories.
In the end, Flutter is not always great. The fact is that it cannot be balanced with a bowl of water. Of course it's just a matter of deciding where to put it. Flutter can still be used easily and efficiently.