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

This article introduces the knowledge of "what are the web application skills that are designed to be used". In the operation of practical 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!

Tip 1: pay attention to the tab

Tabs have a good concept of visual expression in the organization of content. Their functions are intuitive, and everyone knows how to use them. Unfortunately, the tab allows lazy designers to make the form out of control and out of order.

Do not use tabs to deal with overly complex forms. Focus on reducing overly complex forms. If it becomes too messy to put it all on a single page, break them down into a wizard.

Tip 2: make the save behavior consistent

Do not mix autocommit with manual save behavior. If there is a save button, the user will no longer trust the autocommit behavior. By the same token, they may assume that autocommit will be processed in other types of input, thus ignoring the save button. No matter which method you choose, stick to it and ensure consistency.

Tip 3: consider the location of the delete button

Unless the user needs to delete something frequently, you should put the delete button in a secondary place in the form. Providing a delete button in search results may add unnecessary complexity, thus overemphasizing behaviors that you may not want users to use frequently.

Tip 4: always provide a label for the input field

It has become a popular trend to use blank prompts instead of input box tags in web applications because the application looks simple and clear. Unfortunately, when the user enters something, the blank prompt disappears. What if the user wants to know which input box is what data?

Floating tags have become a new and popular solution between distinguishing between the simplicity of user placeholders and the use of fixed tags.

Tip 5: do the right research when there are new needs

Most users do not know how to design software, but they often put forward requirements for software design. Ask them why they need something new and understand what they really want to accomplish. Provide a better solution for potential requirements, rather than blindly delivering new features.

Tip 6: balance interface intuition and efficiency

When users use your application for the first time, they need to get started as quickly as possible. Users will never consult the documentation and will not get any training in most cases. That is, over time, users will shift from trying to learn how to use it to using it very efficiently to get the job done within eight hours a day.

There is a delicate balance between making the application easy to use and keeping the screen simple and efficient and fast.

Tip 7: what happens after saving?

Always consider what happens when the user clicks save and submit. The result must be consistent, and the user needs to know the response information somewhere. If your application has a typical search-edit-save concept, the right thing to do is to display it on the search results page, as they may be preparing to move on to the next item in the list.

If the user has completed multiple steps in a wizard interface, a completion page is required to show what is saved and provide options for the next step. New users may be confused if there are no next actions or suggestions on the wizard's confirmation page.

Tip 8: where is your current position?

In a large web application, there may be dozens or even hundreds of interfaces. Users always need a consistent way to know where they are in the application and what they are currently editing. This allows you to highlight where the user is in the application through the navigation bar.

You can also navigate breadcrumbs to describe the location of the user in the application. Breadcrumbs (breadcrumb navigation) can also display every place selected by the user, and you can click one of them to return to the interface they last browsed.

Tip 9: don't dwell on the scroll bar

A typical UI design in the era of desktop applications is to adapt to the screen without scrollbars. A vertical scroll bar is not a bad thing in web applications, as long as it is visible and clearly displayed. When the user clicks on the form tab, it even scrolls to the appropriate location automatically, depending on the browser's behavior.

Tip 10: don't be afraid of blanks

There is a natural tendency to try to fill everything. As the demand grows, developers force more and more features into a limited space. The rest is an overly complex application that looks quite complex and confusing. Leaving the right amount of white space can make your application look simple and approachable.

This is the end of the content of "what are the tips for designing web applications?" 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.