Describe the bug
Flutter on the web builds the application into a single app.js file or app.wasm file for rendering.
In terms of applications this is correct but for standard websites this is bad due to long load times and potenital cache mismatches between entire versions.
A resolution to this is deferred loading, supported on both web and android (but not necessary on android). Which when compiled will split the application up into multiple js or wasm files for load when needed. I.e, admin.wasm, match_controller.wasm etc... Which can help the load times, especially for scoreboard displays which only need small parts of the functionality that TMS provides.
This does however increase the issue of cached versioning. mismatched versions between their segmented parts may become more problematic. But versioning systems in place have mentioned this issue and have a few ways around it.
https://lukasnevosad.medium.com/our-flutter-web-strategy-for-deferred-loading-instant-updates-happy-users-45ed90a7727c
flutter/flutter#127459
Steps to reproduce
No response
Logs
Expected behavior
Fast loads (1-10 seconds) on slower networks.
Updated redownloads on newer versions of the files on web.
OS
Web
Additional context
No response
Describe the bug
Flutter on the web builds the application into a single app.js file or app.wasm file for rendering.
In terms of applications this is correct but for standard websites this is bad due to long load times and potenital cache mismatches between entire versions.
A resolution to this is deferred loading, supported on both web and android (but not necessary on android). Which when compiled will split the application up into multiple js or wasm files for load when needed. I.e,
admin.wasm,match_controller.wasmetc... Which can help the load times, especially for scoreboard displays which only need small parts of the functionality that TMS provides.This does however increase the issue of cached versioning. mismatched versions between their segmented parts may become more problematic. But versioning systems in place have mentioned this issue and have a few ways around it.
https://lukasnevosad.medium.com/our-flutter-web-strategy-for-deferred-loading-instant-updates-happy-users-45ed90a7727c
flutter/flutter#127459
Steps to reproduce
No response
Logs
Expected behavior
Fast loads (1-10 seconds) on slower networks.
Updated redownloads on newer versions of the files on web.
OS
Web
Additional context
No response