How did I find this book? I have taken some courses, and my lecturers often discuss them. I wasn't convinced to read at first because the title is obvious - don't make me think. As a designer, I should conduct research to find the easiest way and provide the best recommendations. Right? What can I find new?

I started reading this book. While reading, I feel like the Internet was trying to copy it just by putting in its own words. But nobody wants to tell the source. Reviewing a book is not about telling others what's inside, but about what you learn and how it can help you improve design. In my perspective, it is possible that a more experienced designer could provide additional insights regarding certain aspects. And does not try to rewrite the book or tell everyone that everything that they find in the book is perfect.

Consistency.

I was suprised with statment

Simplicity is more important than consistency.

I already designed web apps. When I considered my examples, I began to ask questions and analyze. Do simplicity be more important than anything else? What if consistency is simplicity because it gives to the user comfort? The users learn scheme. The scheme should be easy, fast to learn and repeatable. Furthermore, I started to believe that the designer is not skilled enough. And you are rich. Because developers have to spend extra time to change the same element.

Example

If I design the element to represent connected devices to the computer. I need to predict states and list of available devices. Now I don't know where I will use, but still if I work on the same project for a while I could ask a client about the plans. I can ask for a vision. Maybe this part already should be short version and have a 'show more' button?

It's strange that a designer is not prepared for a work. Research in this case is short. And you don't need to have experience with designing such a thing.

Anyway. I will use this element several times. And what? Suddenly, I will redesign it just like that? Because what? Will the small thing be changed? And it will be added to different context, exp to dashboard? I would consider it a storm in a teapot. Try to empathize with a user. Suddenly, the user will start to use a similar component, but it will force the user to use it differently. Can you imagine what will happen? The user will feel confused. Next, the user has to learn again how to use the new version of the component.It's a risk that the user will drop the website and will not do it or will avoid this place. Have you installed the heatmap tool? If you don't do it better, the user will learn it, of course. But how much does it cost? The time that is spent on learning. Time is money.

When I think about simplicity and consistency, I would rather say:

Create a simple component and apply it consistently throughout the project. Don't redesign a component every time differently. Try to be creative and find ways to do it effectively. Respect developers time. Try testing it if you see that the change is needed. Try redesigning the component and seeing if it will work for every occurrence.

The basics of billboard design.

I like this chapter, good one but… I don't like terminology. Someone might think that they could design a billboard after reading this book. It's a mistake. Here you can read only about website design, not about anything else.

What are billboards, and how should they be designed? It's the basic thing than you can imagine. Where is a billboard? Up, far away and in the city where are big traffic. It is a large photo with only one information. No one will see it for 30 seconds. A good example is market add - logo, the product, price and text - promotion. Some companies can use it to positioning their brand. You can add a good picture. It's best if the person is going to show up with the company's product. The model can interact with the product. Add a logo and slogan. I appreciate billboards that have a compelling concept, and they can be humorous or unconventional. The most memorable designs are emotional - make you smile, happy, sad, or inspired.

The book doesn't contain these suggestions. This book talks about what websites should have. Tips contained in the book will be more usefully when you will design a catalog. But wait. Websites sometimes would catalog, right?

What do I appreciate about the author?

There are many books recommended by the author. I like it. He is someone who I see as confident and competent. He recommends books that are worth reading, and he avoids stealing them. Furthermore, he could increase the price if he rewrote mentioned books as his own.

Allowed clicks.

When you start out as a UX designer, you should know that the flow should contain as few as possible clicks. It isn't a negotiation.

Navigation on the website.

Instructions should leave and be replaced by better flow, user experience and content. It's so true.

Chapter 6 has a better title than the one before. You don't even have to do detailed research. I had a client who suffered because he was unaware of where he was. He tried to upgrade his old web app. Poor navigation and no breadcrumb made everyday use of the app difficult. This was on the long list to change web app.

When I read this chapter, I realized that the user had to learn how to use the internet before. I've told my mum about the Internet and how to use Facebook. The Facebook interface is not easy to use. There is no onboarding or tips at all. They have a help panel, but it is difficult for someone who has never used it before to type the correct question. I remembered my first classes in primary school when the teacher showed us how to use a computer and what the internet is. Learning is fun and interactive, so we can learn quickly and easily. Age doesn't matter.

The Big Bang Theory of Web Design

Reading this chapter, I realize that the book is not for everyone. Not for small business that need only a one-page website, but for someone who will sell products and services by an Internet.

There is nothing worst than first visit on home page with no idea what's to do next.
[Steve Krug. Don't make me think]

Every web page and application is described in the quote. Unfortunately, the clients don't get it. What's next for the user? We have to tell him/her or show him/her. Sometimes the home tab is also a table of content. But we can still think of video or animation to show the offer.

The Farmer and the Cowman Should Be Friends

I appreciate how the author describes the product team. Everyone looks at a product differently. Also, I'm curious about the developers he met. Does the customer want a product that works well? Who should be a pleased, the client or the developer? What's worse to lose? Clients appreciate websites that are attractive. It makes using the website more enjoyable, and there is already scientific research that what is pretty gets more trust. If we use animations, the experience will be better. Don't forget about flow, that needs to be simple. All these elements make products excellent.

The author tried to explain the difference between the art and commercial design. I think he doesn't really understand what art is. A work of art is created by an artist. It's a product, but it's in a different category. Wouldn't you compare bread to a car, right? There are products, but they are not the same. This is why the art should not be compared to the application or website. I think that discussions like this are pointless. If the digital art were an art or a commercial design, then everything would have the same name. Different labels show us that we shouldn't treat things the same way. That is why a website or app should be functional and appealing to the eye. Even if an interface looks good, it's not art. It should not be overloaded with information or empty. An internet should make our lives better, not harder.

That's it. No more thoughts.

I like this book. It's a good knowledge compendium about websites. There isn't too much unnecessary information. Only what the author thinks important. Of course, this book should not be only the one for designers, but one of many. You won't find everything. I appreciate the book because some philosophy can be used when designing a web application.

I hope that you found something new. Also, I read a book a few years ago and still don't regret it. I use some things that I found there every day at work.