What is the deal with Graphical User Interface/app psychology?
Like where is the goto psych/CS UI 101 class/book/YT that over simplifies but grounds someone with no background or previous knowledge? Maybe something like the "Blender Doughnut" of great UI design?
I've changed UI twice with an app recently. I have a slight intuitive grasp of what I don't like, but I lack the language and depth in this niche to express the emotional response well. I have no clue where to start with my own designs if I ever felt motivated to create one.
There is a decent amount, these companies just like to ignore it. Problem is, boring familiar design is best design, but that's not what gets the interest and jobs
It's not just that companies like to ignore it, it's also that they have incentive to make shitty UI if it means they'll make more money off it (e.g. intentionally showing things in searches that people weren't looking for in the hopes that they might click/engage/purchase)
We ought to stop calling it UI when it's not meant to benefit the user anymore. A lot of changes are probably more accurately called VCI because they are dark patterns meant to benefit the VC instead of the User.
Excellent book. It's very far from hands-on, and doesn't even address UI in particular most of the time. Won't tell you how to lay out anything, but puts you on the right empathetic mindset for design in general.
Based on OP's description, might be just the ticket, but may also be too general for some tastes.
Indeed, this book is an excellent starting point and it's a little disappointing it's not upvoted further simply because it isn't aimed at Graphical User Interface. It's still about how people think things work, and how to make them work how people think they work.
Mid-to-late 00's had best UI design. Nowadays everything is less-functional and to do simple tasks you need to click through 5 different menus, and move your fingers in all directions, because there's no standard to do anything.
Just to see my watch later playlist on YouTube on my phone I need to click 2 buttons, scroll down through playlist list and click on the conventionally placed watch later playlist on the bottom of the list. What the fuck?
I wonder what all these UI specialists even do. Just blindly do everything upper management tells them to do, even if that makes no sense?
Speaking as a designer, it’s important to separate the style/trend of a UI from its function. I think what you’re looking for is actually UX design.
As a discipline, User Experience uses evidence-based research to understand how and why users behave they do. This leads to specific design patterns and principles that underlie all the good UI design seen from the giants like Apple, Google, Microsoft, etc. It gives you the language to evaluate designs. This is the foundation of your UI and the rest is just style — fonts, colors, imagery and icons which is subjective and less important. I lost ambition to be a trendy UI designer, so every design looks the same, but usability will shines through. Clean, simple and accessible is timeless.
Study the articles from nngroup.com. They pretty much established the field of UX Design, with content talking about user behavior in the 1990s. https://lawsofux.com is a more attractive and consumable option, also heavily influenced by NN Group. Finally, accessible design is good design for all, not just those with disabilities. Understand the guidelines set by the W3C for accessibility, like minimum font sizes or contrast ratios for colors.
Alan Dix’s book (aptly named “Human Computer Interaction”) is quite good, even if somewhat old by now. HCI is an actual academic discipline with, yes, tons of theoretical and empirical results that govern what a good UI should be. Many of which are indeed grounded in psychology, others in physiology, etc (what we call Human Factors). There is a whole special interest group of the ACM just about it: SIGCHI.
Do not confuse this with fashion/trends/taste. These change, resulting in widely different possible flavors of UI over the years. But the underlying principles are the same.
Another thing to remember is that the fact that Apple, Google, or someone else implemented an UI in a certain way doesn’t mean they are following best practices and guidelines. Novelty sells, even if at the end of the day it does a worse job of things…
Begin with The Design of Everyday Things. Is it specifically for tech or software? No and barely touches on it, but it outlines what UX is for and provides easy to imagine examples of realistic conflicts and solutions that are eminently realistic.
The ultimate goal is always intuitive interaction. I can’t appreciate the beauty of a functional object after it’s frustrated me when I tried to use it
The book “Design of Everyday Things” might also provide some good background.
And then there are the endless Human Interface guidelines put out by Apple and many other companies that usually try to explain the “why” behind their decisions.
It may not be exactly what you’re looking for, but if you’re interested in user interface, I can’t recommend this book enough: GUI Boopers by Jeff Johnson
A UI isn't just an app, or a program running on a screen, everything man has built to interact with by others have a UI, from simple tools cutlery, to complex industrial control systems.
UI design has a very simple goal, "simplify usage", from the shape of the handle of a knife to a color coded matrix of indicator lights at an industrial monitoring system, it all comes down to "simplify".
Unfortunately there are just so many, many different needs of the person interacting with different systems that there are very few exact rules to follow.
You mention apps, so let's limit outselves to software...
The first question that the UI designer needs to know is "what should the UI allow the user to do".
It could be as simple as "register a smartphone when issuing the phone to a user".
This means the UI needs to accept input of six pecies of data:
Manufacturer of the phone
Model of the phone
IMEI number of the phone
Name of the user
Date
Name of the person issuing the phone
Ok not that bad, so you make this, but then you quickly realize that the user of the system needs a way to check if the phone was added to the system correctly.
If this is just added in Excel, then it is a solved problem, but if you are building a completely new system, then you need to add a way to get a list of all phones issued in the system to the UI, you also need to add a way to update posts in the list.
Then you realize you it would be very helpful to have a way to see the actual status of phones in the system, there will be times to log if a phone is sent for service or if it gets stolen or so, so you add a status field.
After a few months of accumulating data, the list looks good, if a bit messy, you can't get a good overview of it.
So you add color coding to the status field, white for in storage, green for in production, yellow for on service, red for lost/stolen, grey for retired.