User Story: As a developer I have an efficient inner loop building .NET MAUI apps

[davidortinau]

Summary

In .NET 8 we continue to pursue improvements to the reliability of Hot Reload as well as build performance in order to reduce the amount of time between when the developer makes a change and can verify that change in a running app (aka inner loop).

Tasks

• Add MtouchLink command to support XAML Hot Reload for iOS Devices #8429
• Setter Specificity #11082
• Changing <DataTemplate/> contents can give a runtime exception #11203
• XAML Hot Reload is broken within Shell.TitleView #13992
• iOS Debugger Indicates App Has Terminated Immediately #9056
• Updating shell Tab title doesn't work via Hot Reload / code behind #15659

[shadowfoxish]

This may only apply to grids (with auto sized rows/columns) and collection views and those sort of template-y components, but in the XAML Live Preview, it might be interesting to trace what bindings or calculations/components are taking the most time relative to the whole for a page load. Could lead to things like "hey, this complicated binding expression is taking a long time to evaluate" or "the scrolling on this page is not smooth/impacted by these sub components the most".

I get a lot of messages in the debug console like "[Choreographer] Skipped 57 frames! The application may be doing too much work on its main thread." and "[View] [ANR Warning]onMeasure time too long" and "[View] [ANR Warning]onLayout time too long". Could be useful to expose that information in a more actionable way.