β‘ Bolt: Optimize AppIcon with ThemeExtension #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π‘ What
Refactored
AppIconto use aconstconstructor by replacing the mutableAppIconDefaultsclass with an immutableThemeExtensioncalledAppIconTheme.π― Why
The previous implementation of
AppIconused a mutable, static class for default values, which prevented the use ofconstconstructors. This meant that every instance ofAppIconwas rebuilt whenever its parent widget rebuilt, even if its properties hadn't changed. This causes unnecessary work for the UI thread.π Impact
Reduces widget rebuilds significantly on screens with many icons. By using
const AppIcon, Flutter can skip rebuilding these widgets entirely, leading to a smoother user experience and lower CPU usage.π¬ Measurement
This can be verified using the Flutter DevTools Performance view. Before the change, rebuilding a screen with many
AppIconwidgets would show a large number ofAppIconbuilds. After the change, the number ofAppIconbuilds will be dramatically reduced or eliminated for rebuilds that don't change the icons themselves.PR created automatically by Jules for task 9850015487311353154 started by @Doezer