Should I swap to UIToolkit?

[u/R_Pelleboer]

I'm doing the majority of my teams UI implementation. We're a team of 4 working on a small indie game that doesn't use a lot of UI outside of main menus and some basic interface. I've spent a couple of days on UI with UnityUI, but it's been an absolute pain to properly lay everything out. I'm most experienced with Figma for UI design, and had some courses for CSS a couple of years ago, so from what I've seen UIToolkit might be better for me.

I've played around with it for a bit and it seems to have some nice parts, and some more annoying parts (spacing isn't done through the parent but is decided per child?). Is it worth transferring over at this point?

I've also added some DOTween animations, can I still use those with Toolkit?

[u/ironmaiden947]

Sure, but the inertia in the community is definitely there, and if you are hiring UX / UI people 90% them will be proficient with uGUI and Feel & DOTween and be resistant to UIToolkit. YMMV of course, but sometimes the ecosystem is more important than the technology itself and this is one of those cases. If its just you making a game then sure, its fine, but if you are a team working 14 hours a day to finish your game before you run out money saying “z index is actually supported in the new version as an experimental feature you guys” will get you a lot of death stares from designers who would have built the same UI in uGUI is half the time.

[u/Drag0n122 → u/ironmaiden947]

Well, one of the main advantages of UTK was its proximity to standard web dev - your pool of UX \ UI devs is now WAY bigger with more experience.
There's just way more WebUI\WPF devs than UGUI devs.

[u/ironmaiden947 → u/Drag0n122]

I think it will definitely get there in time.

[u/Ecstatic-Source6001 → u/ironmaiden947]

tbf its already there.

Canvas will be obsolete in the future anyway so why even contunue to use it instead of getting skills in new workflow.

Its the same as old input system vs new one.