Is rebuilding the entire visual tree per interaction (immediate-mode style) encouraged in WinUI 3?

Hi,

I'm working on WinUI3 desktop application in C++ without XAML. I've been experimenting with building UIs in a more "immediate-mode" style using WinUI 3, basically clearing and rebuilding the entire visual tree every time the user interacts with something, like clicking a button or typing in a field.

This feels pretty intuitive for small UIs or prototyping, but I'm wondering if it's something that could cause issues in the long run.

Is WinUI 3 designed around a retained-mode model where the system expects the UI tree to stay relatively stable?Could this kind of frequent UI rebuilding lead to performance problems, like extra layout passes or rendering overhead?

I want to understand whether this is safe to do in more dynamic apps, or if it's better to stick to the traditional retained-mode approach and just update properties/state instead of tearing things down.