-
-
Notifications
You must be signed in to change notification settings - Fork 27
Description
Previously we were going to unify both to keep things simplistic. But I think it's better to put in a little more time and effort for both desktop and mobile users. Going forward, we'd like things to look absolutely crisp on desktop and provide you with as much information as possible without overwhelming you. And then on mobile, the idea is to make the UI efficient and easy to interact with using your fingers. This will require a lot more planning with the UI but it's a one-time thing. And if we create a good standard, then we can follow that for each UI by reusing components throughout the app (i.e. back buttons, submit / cancel, items / cards, text containers, chat box, dialogue box, skills, and more).
-
The first step is figuring out the best way to load the required UI and unload the one that will never be used. Is it efficient to create UI on the fly or should you include it already in the scene? Maybe just include both and disable their processing and hide them as well? This will require some testing.
-
Next up is designing their UI to fit the device type they're meant for. As well as detecting what device is being used. I'd assume Web, Console, and Desktop should go together. And mobile is its own section.
Metadata
Metadata
Assignees
Type
Projects
Status