Reducing XAML UI load time in a Unity project
Posted: 10 Sep 2026, 06:09
I'm working on a Unity project using NoesisGUI where the UI contains around 85 XAML views, 12 ResourceDictionaries, and roughly 40 custom styles. On my development PC, entering Play Mode currently takes about 3.8 seconds, and around 1.4 seconds of that appears to happen while the UI assemblies and XAML resources are being loaded.
The UI itself runs smoothly once loaded, so I'm mainly interested in reducing the initial loading cost without removing shared styles or splitting the interface into unrelated views.
For a project of this size, would you recommend changing how the ResourceDictionaries are organized, loading views only when needed, or profiling the XAML/resource loading path first? I'd also be interested in any practical workflow you've used to keep a larger NoesisGUI UI responsive during startup.
The UI itself runs smoothly once loaded, so I'm mainly interested in reducing the initial loading cost without removing shared styles or splitting the interface into unrelated views.
For a project of this size, would you recommend changing how the ResourceDictionaries are organized, loading views only when needed, or profiling the XAML/resource loading path first? I'd also be interested in any practical workflow you've used to keep a larger NoesisGUI UI responsive during startup.