[UNO 6.0 + WASM] Download size the same as before. Expected?

[DierkDroth]

I started with tests on latest UNO 6.0 and was looking at the download size of my WASM app.

Reading through the UNO 6.0 announcement I got the impression that the download size would be optimized as well. However, when comparing the overall download sizes in Chrome anonymous mode of my UNO 5.7-dev app compared to the UNO 6.0 version I found that number are pretty much the same: ~220 requests, ~28MB transferred, ~95MB resources (F12 - Network tab, footer row).

Here is the list of UNO packages which are in use on my app:

Is is expected that the WASM numbers are pretty much the same or am I missing something?

[jeromelaban]

Thanks for the question. The size numbers are broad numbers that depend on the platform, and optimizations are mostly for desktop builds on Windows and iOS.

For Wasm, some reductions may happen when the Xaml Trimming and Resource Trimming is enabled.

[jeromelaban]

on resource trimming: not sure I understand the feature correctly. In my app I e.g. have support for English and German which could be switched at runtime. Obviously I would not want to trim neither one. What exactly would be 'trimmable' in that case?

Any dependency that provides localization, including Uno itself. The language list you provide will be used to remove unused cultures.

[DierkDroth]

Thanks @jeromelaban. I'll give that a try...

[DierkDroth]

@jeromelaban FYI: the observed gain was < 2% in download size (is that expected?) -> I'll leave that option for now.

[jeromelaban]

It's expected, it's small contributor, particularly when AOT is enabled.

[DierkDroth]

Thanks for clarification @jeromelaban