Deferred Components: On-Demand Features in Flutter

WHY IT EXISTS: To combat app bloat. Large applications suffer from lower install conversion rates and can be slow to start. Deferring non-critical features to a later, on-demand download makes the initial user experience faster and lighter, which is especially important on mobile and web platforms.

THE MENTAL MODEL: It's like a video game that ships with the main campaign and lets you download optional DLC packs later. The core app is fully functional, but extra content—like new features, widgets, or large assets—is fetched from the app store or a server only when the user requests it. This effectively splits your single, monolithic app into a lean base module and several dynamic feature modules.

HOW IT WORKS: You define certain parts of your Flutter app as separate, loadable modules. At build time, the Flutter toolchain packages these as distinct files. The base app contains logic to request, download, and then integrate these modules at runtime. This typically involves using a platform-specific API, like Android's Play Feature Delivery, to manage the download. Once downloaded, your Flutter code can dynamically load the Dart code and assets from the new module.

WHEN TO USE IT: Use this for features that are large and not essential for the app's primary function or first-run experience. Good candidates include complex user flows only a subset of users will access (like an enterprise admin panel), features reliant on large assets (like AR filters or high-resolution tutorials), or optional functionality that would significantly increase the base app size. The source confirms this is for Android and web.

WHEN NOT TO USE IT: Don't defer core functionality or anything needed for the app's initial startup and main user journey. The added complexity of managing loading states, network errors, and version compatibility is not worth it for small features. It also introduces a point of failure if the user is offline or has a slow connection when they first try to access the deferred feature.

ONE CANONICAL EXAMPLE: A news app could ship with its core article-reading functionality. A complex, data-heavy "interactive map of historical events" feature could be packaged as a deferred component. Most users who just want to read the news never download it, keeping the app small. A user who navigates to the map section would trigger an on-demand download of the feature.