Hola, I’m Hieu, a Software Engineer

The app size conversation usually starts after a stakeholder compares the APK to a competitor’s and asks why a to-do list is 40 MB. The engineering response is often to start deleting packages, which is both the most painful lever and usually not the one that matters. Flutter apps have a size floor: the engine, the Dart runtime, Skia or Impeller, and the ICU data. That floor is real and you cannot remove it. Everything above it is yours, and in most apps I have looked at, the majority of “yours” is assets and shipped-but-unused native code, not Dart. So the first move is not to delete anything. It is to measure. Measure first: --analyze-size flutter build apk --release --analyze-size flutter build appbundle --release --analyze-size flutter build ipa --release --analyze-size This prints a summary and writes a JSON file. Open that file in DevTools’ app size tool — it gives you a treemap where the boxes are proportional to bytes, broken down by package, by asset, and by...

The app size conversation usually starts after a stakeholder compares the APK to a competitor’s and asks why a to-do list is 40 MB. The engineering response is often to start deleting packages, which is both the most painful lever and usually not the one that matters. Flutter apps have a size floor: the engine, the Dart runtime, Skia or Impeller, and the ICU data. That floor is real and you cannot remove it. Everything above it is yours, and in most apps I have looked at, the majority of “yours” is assets and shipped-but-unused native code, not Dart. So the first move is not to delete anything. It is to measure. Measure first: --analyze-size flutter build apk --release --analyze-size flutter build appbundle --release --analyze-size flutter build ipa --release --analyze-size This prints a summary and writes a JSON file. Open that file in DevTools’ app size tool — it gives you a treemap where the boxes are proportional to bytes, broken down by package, by asset, and by...

Flutter 3.47 landed on August 13, 2026, and for once the headline is not a feature — it is an architectural split. The design system is moving out of the SDK. Add Impeller becoming the default renderer on every desktop platform and Widget Previews going stable, and this is the most structurally significant Flutter release in years. The numbers behind it: 1,356 commits from 169 contributors, 66 of them first-timers , shipping as Flutter 3.47.0 • Dart 3.13.0 • DevTools 2.60.0 . Material and Cupertino become packages you choose The change everyone is talking about: material_ui and cupertino_ui are now standalone packages on pub.dev , both at 1.0. The libraries still live inside the SDK for now, but the SDK copies are scheduled for formal deprecation in the November stable release . Why this matters more than it sounds: Design systems can now ship on their own clock. Instead of waiting for a quarterly SDK release, Material and Cupertino can iterate weekly. Cupertino in particular ...

The latest stable Flutter release, Flutter 3.44 , is one of the most consequential updates of the year for teams shipping to Apple platforms and the web. The documentation was last refreshed on July 10, 2026, and the release notes read like a checklist of the pain points cross-platform developers have been asking Google to fix. Full iOS 26 and macOS 26 support Flutter 3.44 (building on 3.38) fully supports the iOS 26, Xcode 26, and macOS 26 releases . That is the headline for most teams: as Apple shipped its Liquid Glass redesign and a new toolchain, Flutter kept pace so you can build and submit against the current SDK without hacks. There is one migration to be aware of. Flutter now supports Apple’s mandated UIScene lifecycle , and code migration is required to adopt it. If you maintain an iOS Flutter app, this is the upgrade task to schedule — it is mechanical, but it is not optional going forward. Cupertino Squircles land Apple’s rounded corners have never been simple circles —...