- Published on
[OOUI] The main design book has finally arrived. Object-oriented UI design
Roughly speaking
- The reason it's intuitively difficult to use is because the design is not object-oriented.
- What is Object-Oriented UI Design?
- What the engineers are doing is passing data and rewriting data structures, and what the designers are doing is data representation.
Can it be used intuitively?
One good design is that it can be used intuitively.
It is difficult to meet the point that it can be used intuitively in the digital world, such as the web and apps.
As I look at a number of services, I see that there are many services of the same type that are commonly used and not commonly used.
In particular, B2B SaaS systems handle complex data, so stress is heavy for users of applications that cannot be used intuitively. If you have to read the manual to use it, it's a defeat in the design.
Cognitive load on users accumulates, and users leave and are never used again. The diagram below shows the negative effects of cognitive load.
So what exactly is the design that should be done? How can you create a good design?
There was a hint in a surprising place. It is object-oriented, familiar to engineers.
What is Object-Oriented UI Design?
Object-oriented UI design literally means designing a UI in an object-oriented way, but what is object-oriented?
Object-oriented means focusing on things.
In programs, this refers to creating programs focusing on manipulating things, rather than the procedures that were often often thought of.
When cutting potatoes,
Considering the procedure, we think of it as "cutting the target with a knife" → "potatoes."
If you think about it from an object-oriented perspective, you will think of "potato" → "cutting the object with a knife."
Which is more intuitive when considering procedures or object-oriented? It's definitely object-oriented.
In the case of programs, you will endlessly write code in the digital world rather than in the real world, so writing intuitive code for humans is an important skill from a future operational perspective. As a result, the concept of OOP and object-oriented programming was born.
Let's compare procedures and object-oriented in a real example.
First, the OS. Currently, the OS generally has two UIs: the CLI (command line interface) and the GUI (graphical user interface), but it is clearly the GUI that can be used intuitively. This is because, while the CLI type first as a command, the target file is entered before entering the target file, the GUI decides to do it after selecting the target file.
Next, let's take a look at an example app. The diagram below shows an example of implementing a beef cattle breeding app (!?) on the engineer's information sharing site "Qiita", but it has changed from what you do to object-based (in this case, beef cattle), making it easier to use intuitively.
What do engineers and designers do after all?
A common question is, "What do engineers do?"
For Gonjicchi, the answer has not changed since he first became an engineer.
A person who manages data transfer and data structure rewrite
It is. You may think that he is a person who can organize all sorts of data.
Naturally, skills are required when dealing with data. Images, audio, and video are converted to data to express rich information. Confidential information such as credit cards requires the skills to hide and pass data on, and skills to make it persistent. Machine learning is a skill that feeds data and allows you to spit better data.
What can designers say in this context? Designers are people who aim to express better data. In the context of art, data is both surprising and moving. In the context of web and app design, we aim to achieve more intuitive data representation in the digital world.
If engineers are data manipulation, designers are a profession that focuses on data representation. This book, under the name of object-oriented UI design, is the first time it has been built from the designers regarding how data is handled across engineers and designers. It is a great bridge.