Flutter Null Safety, Code Trim Pitfalls, EngineGroup, and Android Foldable Adaptation

This knowledge bulletin presents several technical topics for mobile developers, focusing on Flutter and Android foldable devices.

Flutter Null Safety : Enabled by default since Flutter 2.0 and mandatory in Dart 3.0. It provides compile‑time null checks, IDE warnings, smaller and faster binaries, and cleaner code. Migration can be done by upgrading the Dart SDK to >=2.12 or adding the comment // @dart=2.12 at the top of individual files.

Flutter Code Trim Pitfalls : The Dart compiler removes unused code to shrink the app size. However, when a condition cannot be resolved at compile time, the related code may be retained unexpectedly, causing the final package to grow.

EngineGroup : Introduced to support multiple Flutter instances within a host app. Each engine runs in its own isolate with separate communication channels, which increases memory usage and data‑exchange overhead, though it enables multi‑instance scenarios.

Android Foldable Adaptation : Adaptation has evolved through three stages—official Android guidelines, OEM‑specific solutions, and Android 12L Activity embedding. Basic steps include adding the WindowManager library, configuring split‑screen rules via XML or at runtime, and initializing the configuration in the Application class.

References: Sound null safety (dart.dev), Lightweight Flutter Engines (GitHub), Android foldable guide (developer.android.com), FlutterBoost (GitHub).