What is web design-Designing for users

web| design As mentioned above, a common mistake in web development is to design a site for the designer, taking into account the needs of the designer rather than the actual user. The process model does not guarantee the quality of a site if the designer ignores the user's needs. Be sure to remember the important principles of Web design:

Rule: The designer is not a user.

What the designer understands is not what the user understands. As a designer, you have direct knowledge of the Web site. You know where the information is and how to install the inserts. You have the best screen resolution and browser settings, and so on. You have to accept the fact that many users do not understand your site as carefully as you do, and their interests are not even the same as yours. Given the importance of the user's interests and expectations, it seems appropriate to make the design appear directly to the user in the way they want it to. But if you take another basic principle into account, that's not a good idea:

Rule: The user is not the designer.

Not everyone is or must be a web designer. Just as you expect a movie audience to guide a movie based on a movie you watch, it's foolish to expect them to design a site just because they're browsing through a lot of sites. Users often have a lot of unrealistic about the site's needs and expectations. Users will not seriously consider a part of the Web site alone. In short, users don't have a comprehensive understanding of the web as designers do.

This means that the key to successful and Easy-to-use Web site design is to think as much as possible from the user's perspective. User-centric design requires the user to be the first person. But what can we talk about users? Is there a typical user? Is there a representative Internet user, and we should design the site for him? Maybe not, but we should consider the general features such as response time, memory and other cognitive and physical abilities when designing a site. A review of cognitive science helps us understand the basic capabilities of the user, which is discussed further in chapter 3rd. Remember, users have personalities when they have commonalities. Things that seem simple to a user can be difficult for another user. Designing a site for users with commonalities may not meet the requirements of all users. A strong user may feel that there are too many restrictions on the site, and the novice will find it too difficult. The user is a group of individuals with certain common abilities and characteristics. The site should also consider individuality when focusing on commonalities, as the following principles point out.

Rules: For the user's common design, but should consider the difference.

Benefits and Availability

A good web site is useful to users. Effectiveness includes two aspects of meaning: usefulness and usability. Usefulness refers to the potential of the site to meet the needs of users of the function. Availability refers to the ability of a user to achieve a specific goal through the operation of a site. For example, consider a site that provides online banking services. It can be said to be useful if it provides the ability to expect users, such as break-even checks, transfers, and money payments. However, the site may also fail completely, and the functionality it provides can be confusing and not effectively used. Obviously, if a site does not work properly, or if it is poorly designed or even flawed, it is not a good site. The available sites are highly efficient and easy to learn, satisfying without errors in achieving the user's goals. The 3rd chapter discusses the concept of usability (U s A b i l T y) in more detail.