General tips would be to use the design thinking method for this:
Everything will hinge on the first part, the understanding/empathizing part. Then ask fundamental questions such as: why am I making a UI? What is the purposes of a UI?
Proper planning saves on a lot of waste later on. For UIs I think composition theory is very important, i.e. getting the user’s eye to where you want it to be (i.e. where it needs to be).
Then do mockups/wireframes and submit the prototype to be tested by actual people. Let them play around with it and record everything they say about it without offering any input, and use that to refine prototype on top of prototype until you have a satisfactory result, then finish up the UI with all the bells and whistles.
General tips would be to use the design thinking method for this:
Everything will hinge on the first part, the understanding/empathizing part. Then ask fundamental questions such as: why am I making a UI? What is the purposes of a UI?
Proper planning saves on a lot of waste later on. For UIs I think composition theory is very important, i.e. getting the user’s eye to where you want it to be (i.e. where it needs to be).
Then do mockups/wireframes and submit the prototype to be tested by actual people. Let them play around with it and record everything they say about it without offering any input, and use that to refine prototype on top of prototype until you have a satisfactory result, then finish up the UI with all the bells and whistles.
I talk more about this process here: https://criticalresist.substack.com/p/how-we-redesigned-the-prolewiki-homepage