Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Converting UI Toolkit into native UI elements on end-platforms

Discussion in 'UI Toolkit' started by v-strelchenko, Jan 21, 2022.

  1. v-strelchenko

    v-strelchenko

    Joined:
    Aug 2, 2019
    Posts:
    13
    Good day, people!

    My question is of a more general kind - is Unity planning to build its UI in a way that it translates into the native UI elements on the respective platforms? An example would be the UI Toolkit input fields becoming native input fields on Android or Web.

    I'm aware that it's not a trivial task, as everything renders as a 3D engine in the end, just wanna know if any thought is given to it.
     
  2. antoine-unity

    antoine-unity

    Unity Technologies

    Joined:
    Sep 10, 2015
    Posts:
    733
    Hello,

    No that is not something we are intending to do.

    Curious to know what specific benefits you'd be interested in ? Native look and feel / UX? Accessibility ?
     
    v-strelchenko likes this.
  3. v-strelchenko

    v-strelchenko

    Joined:
    Aug 2, 2019
    Posts:
    13
    Thank you for the reply, good to know.

    Yes, the native look and feel is something that would interest me. If we go back to the UI Toolkit TextFields, they do look like the native ones, but when you start using them it's the little things that give them away and I feel like the ones that would cause user frustration the most.

    As an example, I have a sign-up screen with multiple TextFields made in UI Toolkit for mobile, and when the person switches between them by tapping, you have to tap the next field twice before you actually start typing: the first tap hides the native keyboard and the second one opens it for the target field. Stuff like that.

    Additionally, with Unity releasing the UI Toolkit, the conversion to native UI elements seems much more feasible for Web, for example.
     
  4. antoine-unity

    antoine-unity

    Unity Technologies

    Joined:
    Sep 10, 2015
    Posts:
    733
    Ok, then it seems that improving the usability of the text fields should be on our radar.
     
    v-strelchenko likes this.
  5. jiraphatK

    jiraphatK

    Joined:
    Sep 29, 2018
    Posts:
    251
    This is a nasty papercut that's been plaguing Unity since forever. It's a problem with Android screen keyboard implementation that put the app out of focus so you have to tap once to close the keyboard and put the app in focus before being able to interact with in-game UIs.
     
    f4bo likes this.
  6. jiraphatK

    jiraphatK

    Joined:
    Sep 29, 2018
    Posts:
    251
    I'm interested in mostly text related stuffs.
    • The ability to copy text from label, and other actions that can be select with native context popup
    • The android keyboard issue above need to be fixed. No one could make a good chat or form-filling UX with that problem. we can currently overcome this by using 3rd party plugin but this need to be fix on the engine level.
    • Unity does not support OpenType font features that is crucial for modern application such as GPos / GSub table. This mean that all the text rendered inside Unity have wrong layout and does not support languages that need those data to display correctly. It also mean that Unity does not support Emoji. I heard that the TMP devs are working on this. But It's not done so here it is.
    otherwise, I don't think native UI is crucial for Unity Engine since most game almost always have highly customize UI and effect. Native look is just not good enough.