I wish you luck with your project.
I wish you luck with your project.
Off the top of my head, some of the key ideas include:
* Affordances, that objects should have (often visual) cues that give hints as to how to use things * Mental models, that every design has three different models, namely system implementation, design model, and user model, and that the design model and user model should try to match each other * Gulf of Evaluation (the gap between the current system state and people's understanding of it) and Gulf of Execution (the gap between what people want the system to do and how to use the system to do it) * Kinds of Errors and how to design to prevent and recover from them, e.g. slips (chose the right action but accidentally did the wrong thing, e.g. fat finger) vs mistakes (chose the wrong action to do)
What's particularly useful about Norman's book is that these key ideas apply for all kinds of user interfaces, from command-line to GUI to voice-only to AR/VR to AI chatbot. I'd encourage you to think about this book in this kind of framing, that it gives you general frameworks for reasoning and talking about UX problems rather than specific practical solutions.
Design is solving problems so they're intuitive for the user. Obviously a door with a handle shouldn't be a push door, I don't really think you need to write a book about it. And the types of people creating bad design are generally constrained by cost, time, or practicality, not necessarily by education.
Luckily the only emotional need my work fulfills is getting money.
So now instead of one developer lost and one analyst created, you've actually just created an analyst and kept a developer.
More than likely designers are making up work to justify their jobs. Not good for your career if you admit the desktop interface was perfected in ~1995.
I spent $1000 on a Macbook Air, it instantly works with zero headache, has way more app support than Linux, is super fast, and so on.
If I want to play games, I bought the cheapest gaming laptop from Best Buy for like $500 a few years ago and only use that computer to play games.
I will definitely consider adding timelines to future software I make, it's an awesome feature.