The more platforms a Flutter application supports, the more code a project can have that is needed only for one platform and not needed for others. How to make sure that unnecessary code does not get into the final platform-specific build? And how to check that it really did not get?
In Flutter, there is a Tree-shaking mechanism, which is designed exactly for these purposes. Many Flutter developers have heard about it, but not everyone really understands what it is and how it actually works. Let's try to figure it out.
EPAM Systems
Chief Software Engineer, GDE in Flutter and Dart
Aleksandr is an experienced software developer with a rich background, in IT for more than 20 years. He worked with different stacks in backend, frontend and mobile fields, but since 2018 his main interest is Flutter. Aleksandr is a Flutter and Dart GDE and Head of Flutter Discipline in EPAM Systems.
Aleksandr is an experienced software developer with a rich background, in IT for more than 20 years. He worked with different stacks in backend, frontend and mobile fields, but since 2018 his main interest is Flutter. Aleksandr is a Flutter and Dart GDE and Head of Flutter Discipline in EPAM Systems.
Cognizant Netcentric
GDG Organizer
Antreem
GDG Organizer
Kantar XTEL
Lead Frontend developer
TrueScreen
Organizer
