Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "what are the most common mistakes made by UI designers". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Ignore the functional category of the product

Sometimes designers introduce functions into the product that make the whole development process more complex without adding any added value to the product itself. While prioritizing the design function, it is important to take into account the business objectives, the scope of the project, the timeline of the product, and the way it is developed.

For example, we are designing a function option for users to upload personal avatars, but if we add cropping, zooming, rotating and other functions in addition to the "upload" function, this is itself a complication of the original function.

It may be very convenient to add "rotate" and "cut" buttons to the design, but it is hard to say in the specific development and implementation. Do you want to call existing functions, add open source components, or write code from scratch? It's all going to be a problem, and it's full of unknown. From a product and team perspective, the safe choice is to avoid adding features as much as possible unless they are determined to be extremely high priority and essential for the entire application. Always put business and user goals at the forefront of the design process.

2. Not ready for the handover

In the modern product design industry, your design or material may be invoked upstream and downstream. When designing, we should consider who else will use the content of our work. Whether it is to be handed over to developers or other designers, the relevant content and materials must be organized as reasonably as possible.

Take the design file of the UI design as an example, where each artboard should be correctly named and arranged horizontally so that it can be clicked and opened in a logical order.

We should have a well-organized design file that contains icons in SVG format, as well as other image materials that should have a high-quality version.

Zeplin is my preferred collaboration tool in my daily work. With Zeplin, developers can easily get code snippets, size parameters, spacing data, font size, SVG material, and so on.

Such seamless switching can make the whole process smoother and the efficiency of team cooperation greatly improved.

3. Ignore the user's usage scenario

When designing interface interaction, it is very important to consider the environment of the user, because there are many environmental factors that affect the interactive decision. Consider where users are when using our APP, how much time they have to operate, and what their emotional state is, which is the basis for designing interactions.

A sleep cycle type of APP is a very typical case. The APP uses a relaxing dark interface, making it especially suitable for users who set their alarm clocks before going to bed.

You can see good or bad cases in a variety of different places. For example, navigation apps should allow users to click as little as possible, Kindle will try to make sure that reading in the sun is not dazzling, while note-taking apps can be used offline, and so on.

4. pursue the effect of high fidelity

In the stage of verifying ideas and exploring solutions, it is best not to go for high-resolution visual effects, which is the easiest mistake to make.

In fact, this is not so much a mistake as a time-wasting choice.

When we want to combine different ideas and explore layout and hierarchical construction, it's best to use tools like Whimsical to draw wireframes, which is faster and lighter. When it's just a wireframe, it looks really rough, and it may be hard to fall in love with it, but it makes it easier for us to receive feedback and explore functions.

5. Ignore users with behavioral disorders

When designing a digital product, it is like creating a public building such as a library or school. it must be for everyone, including users with physical disabilities, color blindness and visual impairment.

Domino was once sued by a blind user because he could not access Domino's website. In fact, in today's product design, taking into account the blind and color-blind users is completely feasible.

Usually, we try our best to make the product look good to ordinary people, ignoring the relatively small number of users with behavioral disorders who are different from the normal user interaction pattern.

Reducing text to 8px or using very light gray can make the design visually hierarchical and expressive, but it gives visually impaired users basic accessibility.

On Dribbble, we will see a lot of these designs with accessibility barriers, which will be problematic if they are copied directly into the real product.

For example, the contrast requirement of 4.5 in the Web content accessibility Guide (WCAG) is not met by many designs. In addition, there are detailed indicators for motor, auditory and cognitive impairment.

Of course, you can also use Stark to check that your design conforms to these accessibility specifications.

6. Copy other people's works or blindly follow the trend

For designers, trends are a bit like junk food. Indiscriminately following trends can bring you some "seemingly obvious but very cheap" solutions that give back in the short term but are worthless in the long run. Designers who follow the trend will soon have a bitter taste of it. What kind of feedback will you get in the end to follow other people's designs? The only reward is a sense of emptiness. -- designer Micah Bowers

You may easily get caught up in the world of Dribbble, soar in beautiful animations and gorgeous gradients, and then quickly forget your original design goals.

We are really fascinated by discovering special interaction and design styles on platforms like Dribbble and trying to apply them to design. However, it is absolutely different between being inspired by novelty and copying blindly. Learn from it reasonably, use it flexibly, and don't plagiarize.

7. Ignore the established design language

At any time, breaking with conventional design, users need to spend more time processing such information. Designers need to take into account the limitations of human cognition and the limited ability to remember. -- Joanna Ngai

After so many years and so many digital products, users have relatively clear expectations for APP, websites and software. if their functions and experiences do not meet expectations and are not "intuitive" enough, they may be frustrated.

The most typical case is the design of icons. There are very clear expectations for icons for functions such as "search", "home page" and "collection". If your design deviates too far from cognition, the biggest headache must be the user-they don't know what your icon represents.

8. Focus on visual rather than actual operating mechanisms

One of the things that every UI designer hates most is to break the design they create.

To break the design, the most common situation is to input information and trim the layout for daily use and use. But in order to make the product and design flexible, scalable and user-friendly, the "perfect design" that exists only in the ideal state must be broken.

When I am designing an APP interface, if the name entered by the user is only a dozen letters, it will look simple and elegant, but when one is called Hubert Blaine Wolfe ­schlegel ­stein hausen ­berger ­dorff Sr. When the user enters his full name. What's going to happen?

When testing the entire design, it makes sense to take a step back and make sure that the entire interface takes into account the actual situation.

9. Lack of complete and effective state presentation

In the actual design and development, the different states of UI controls represent different meanings and directions. Without any one, the experience and even the function will be much worse. At this time, there may be developers to supplement, but usually such a supplement will make the design lack of unity and bring more problems later.

In the case of buttons, we must take into account different states, such as error, activation, disable, hover, null, fill, load, and so on.

When I am designing a wish list application, I need to give priority to the empty status when the user has not filled in anything. Without this, the whole experience would be far worse.

10. Redesign native UI components

Through the existing components of the original platform, UI designers can quickly create an experience that is familiar to users and avoid typing errors.

No matter how good designers we are, it's hard to design a date selector for the iOS platform from scratch. Even if you design an objectively better date selector, on the one hand, users need to relearn the use of new components, and on the other hand, it is unknown whether you want to match more things for this new design. and how much work on the developer's side will swell.

Making good use of the original native UI components can save too much trouble, save the whole team time and energy, and reduce the cost of user experience.

This is the end of the content of "what are the most common mistakes made by UI designers". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.