If you'd like to only consume the underlying UX scripts (for example, if you're building your own custom UX component libraries) you should only take a dependency on the UX Core package. UX Core doesn't include any dependencies on our assets, visuals, or solvers. If you're building your own custom UX components, you can avoid unnecessary dependencies in your project by only consuming UX Core.

The UX Components package includes ready-to-use prefabs for Canvas layout environments. These prefabs implement the new Mixed Reality Design Language.

These prefabs use all of the RectTransform layout, alignment, and design tools that Unity offers as part of Unity UI. We strongly recommend that developers gain familiarity with the UI tooling that already exists as part of Unity, as experience with Unity UI will also apply to building UI with MRTK3.

While Canvas-based UI will be the right choice for most situations, it might not always be the best fit for your application. Certain workloads can see improved performance by using non-Canvas-based UI rendering, such as some UI layouts where massively batched rendering can reduce drawcalls. For more information, see this comparison table.