* If you use the same resource on more than one XAML file, consider defining it in UBIKThemes (Resources Folder -> LocalState/XAML) rather than on each page. <br>
* Don't define UI elements you don't need for composition and use the default control templates whenever possible (these templates have already been tested and verified for load performance). <br> <br>
Useful links for inefficient XAML code: <br>
* https://www.codemag.com/Article/1509091/XAML-Anti-Patterns-Layout-SNAFUs <br>
* https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-xaml-loading === Using 'NextLevel' bindings ===Performance can be impacted by attempting to show multiple levels of data (ie. child data, from the parent object) outside what is delivered by UBIK by default. For an in-depth explanation, and guidance on how to implement such functionality safely, please refer to this page [[Object hierarchy in XAML: NextLevel, ParentLevel, LinkedLevel]]. [[Category:XAML|XAML Best practices]]
== Testing of UI ==