I really like the new UI for its separation from the MonoBehaviour eco system, give us more flexibility. Using UIBuilder to build your UI de-clutters the heirarchy for complex UI's. I have a UI heavy game that would have been easier to create with a hell of a lot less clutter. I've already got a working solitaire game that is completely done with UITK, even with the minimal drag and drop functionality at runtime. One thing I don't like is the fact that I can change parents but I cannot keep the current root/world position of an element, all positioning is relative to the parent. Which is something I find a bit confusing. Position can be relative or absolute. Both of which are relative to the parent. Which means both are relative, absolute merely removes that element from being included in the layout. There is no way to set an actual absolute position that would be local to the root/world and not the parent. I think you guys are headed in the right direction. Waiting on Input System support so I can replace uGUI in another project I have. Some questions in regards to complexity. How well does uxml handle nesting? If I create the entire UI in one uxml file showing and hiding each part, how well will it perform? Is it better to use separate UIDocuments for each part?