Dev

Flutter 3.47 Release: UI Library Separation and WebAssembly as Default

Google officially released Flutter 3.47. UI libraries are now separate with independent update cycles, and WebAssembly generation becomes the default.

3 min read Reviewed & edited by the SINGULISM Editorial Team

Flutter 3.47 Release: UI Library Separation and WebAssembly as Default
Photo by Mohammad Rahmani on Unsplash

Google officially released the latest version, Flutter 3.47, for its application framework based on the Dart language on August 21, 2026. According to a report by jniino of Publickey, this release is a significant update that enhances the flexibility of the UI architecture and improves support for the Web platform.

UI Library Separation and Independent Updates

The most significant change in Flutter 3.47 is that the UI libraries, “Material” and “Cupertino,” have been separated from the core framework and released as standalone packages. Material adheres to Google’s Material Design and is used for building UIs for Android, Windows, and Web. Cupertino adheres to Apple’s Human Interface Guidelines and is specialized for building iOS UIs. Traditionally, these libraries were bundled with the Flutter SDK and depended on the release cycle of the entire framework. However, starting from 3.47, they are released as independent version 1.0 packages with their own separate release cycles. This allows developers to update only the UI libraries quickly without needing to update the entire Flutter SDK. For instance, when Apple’s design guidelines change, the Cupertino package can be updated and reflected immediately. Furthermore, this separation is expected to lay the foundation for easier construction of custom design systems in the future.

Shift Towards Default WebAssembly Generation

When generating a web application with Flutter, unless a specific option is specified at build time, it currently produces HTML, CSS, and JavaScript from the code. With Flutter 3.47, it has been clearly stated that WebAssembly will also be generated by default in the future. While WebAssembly generation is currently possible via a build option, in future versions it will automatically be generated as a component of web applications without requiring an option. Since WebAssembly enables near-native execution speeds in a browser, significant performance improvements for Flutter-based web applications are anticipated. This strategic shift could further solidify Flutter’s position as a powerful option for web platform development.

Preparation for Future Support and Other Updates

This release includes preparations to support iOS 27, macOS 27, and Xcode 27, which are expected to arrive in the fall of 2026. Early support for Apple’s new operating systems is essential to maintain Flutter’s competitive advantage in cross-platform development. Additionally, it has been reported that the phased deprecation of Intel Mac support is beginning. This suggests a restructuring of development strategies predicated on a complete migration to Apple Silicon, and developers will need to pay attention to future build environments. Numerous other minor improvements have also been implemented, with details listed in the official release notes, “What’s new in Flutter 3.47.”

Editorial Opinion

In the short term, the separation of UI libraries will bring changes directly impacting developers’ workflows. By decoupling library updates from framework releases, improvements in design and accessibility can be reflected more rapidly. This will be particularly beneficial for enterprise applications and products where maintainability is crucial, as it simplifies dependency management and helps reduce maintenance costs. On the other hand, this may also introduce new challenges in managing version compatibility between the libraries and the framework.

In the long term, making WebAssembly the default will fundamentally alter Flutter’s web strategy. Until now, the primary focus was on native app development, with web support being optional. However, with WebAssembly as the default, developing high-performance web applications emerges as a primary objective. This trend could accelerate Flutter’s expansion into performance-intensive fields like cloud gaming and complex web tools.

The question the editorial board poses is whether this technological evolution will truly enrich developers’ choices.

References

  • “Fluter 3.47正式リリース。UIライブラリが分離され独立してアップデート可能、デフォルトでWebAssemblyを生成する方向に、など新機能”, by jniino — Publickey, 2026-08-20T15:02:15.000Z (ARR)
  • Source URL: https://www.publickey1.jp/blog/26/fluter_347uiwebassembly.html
Source: Publickey

Comments

← Back to Home