Repository navigation
Avoid FLX file generation. #9900
Description
FLX files were created for reasons that don't seem to be important anymore. However, having assets in a compressed archive within the application bundle (which itself is compressed when delivered via the stores anyway) adds overhead when accessed. In this trace attached below, to locate the asset in the compressed archive and copy it out takes about 4.5ms. We should consider not generating FLX files and packaging the assets directly in the application bundle.
Activity
sethladd commentedon May 8, 2017
head's up @mit-mit @devoncarew
tvolkert commentedon Jul 6, 2017
Asset variants currently aren't wired up correctly inside Google because we hand-rolled our own FLX building, and it got stale (asset variant file layout has since been redone a few times). Removing FLX would simplify things a lot on that front too.
mit-mit commentedon Sep 1, 2017
@chinmaygarde would this also enable #11892 ?
Hixie commentedon Dec 20, 2017
@szakarias is making great progress on this.
This is a top priority for the current milestone.
szakarias commentedon Feb 14, 2018
The work for iOS and Android is done, will keep this open until all the FLX related code is removed.
szakarias commentedon Mar 9, 2018
Closing this and tracking the final FLX cleanup in #15338.
github-actions commentedon Sep 3, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.