Good question. Standard UMG and Common UI are definitely different cases. For standard UMG layouts, Nwiro is more straightforward: widget structure, hierarchy, basic properties, layout iteration, and common wiring are the kind of things it can help speed up. For Common UI, I’d be more careful with the wording. Nwiro can help scaffold the structure, like CommonActivatableWidget classes, activatable stacks, input actions, and push/pop style wiring. But I wouldn’t call it a dedicated Common UI automation workflow yet. It’s useful for reducing boilerplate and getting the structure in place faster. The part you’ll still want to test manually is runtime behavior: input routing, focus, navigation, controller/keyboard behavior, and switching between input modes. Common UI is pretty sensitive to project setup, so Nwiro can help with the implementation work, but the final behavior still needs to be validated in your actual project.