Friday, 2 January 2015

Build a Web Application design

Web applications are more challenging to create design and the website. Designer wants to anticipate user of behavior, make users’ lives easier and make the experience as visually appealing as possible. Lot of designers tends to do what is easier for them than think about what’s easier for the user. A small tips that designers often overlook in the process of designing a web application.

1. The Power of a Good Tooltip

When you present your web application to a potential customer, If you want to do is ruin your lovely graphic design work by plastering words everywhere to hand hold your new user. Tooltips of your icons can use in a big way. Tooltips offer using the ability to learn a system by exploring icons without harming they are experience. People who are learn what all the buttons do can feel immersed in the experience. When it has been a mobile display, you can use a button that toggles the tooltips off and on. The first you can tap your display the tooltip and the second tap would submit the action.

2. Don’t reply on the User’s Memory

There is nothing more frustrating than flicking between pages or tabs where the information you need on page 2 was entered on page 1. A website app should not force users to remember their details. This should simply allow them to do whatever action they need to do, and presenting them with the most wanted information possible to help them complete their task. If the user is required to entering their customer reference number at the beginning of a process, they will not have to re-enter that information a second time. If you can must ask a user for more than one piece of information that they have to reference elsewhere (bank statement, order reference etc.), you can make them does it all on one page to prevent cognitive overload.

3. Offer Multiple Methods of Execution

Any web app you create needs to adapt to your user’s behavior and offer multiple routes to the end goal. Let us imagine a task management application. A different task may contain a number of information properties that define what needs to be done (date, priority, description etc.). The default method is to add a task with its associated information properties. However, even though you should also give users a quick method to add a task without filling in the extra information properties. Offer for different routes to reach the same end goal makes your application more dynamic for users, so that can get things done at their own pace.

4. Don’t Go Modal Happy

“Hey look at me, nothing else matters!” That is what modal popup scream to users. There is a modern-day answer to popup windows that are sometimes overused. You should have use models to draw the user’s attention. But if you can force your users to focus their attention at every turn, they would soon get tired and turn off. Another handling tip that’s often overlooked is to allow users to close the modal popup when they click outside of the window on the faded background. Users couldn’t like to our work than they need to, and they have don’t like to shouted at. Using the model popups brilliantly and sparingly helps to keep the user in control of their situation.

5. Give Valuable Status Messages

‘Please Wait…’ and ‘Loading…’ are usually messages you’ll find at the top of a page. They are rarely add to the user experience of the application, but if you could do inform users that the application is busy doing something. There is a problem is when they are small and unnoticeable. People whom miss the status messages become frustrated at the application for not reacting to their input as they don’t realize it is occupied with another task.
For example, when you first load Google Maps a small yellow status message appears at the top of the page somewhere center-left, which can be you may not have even seen it before. While these status can message is present, this map cannot be dragged around until it finishes loading. If it is more important enough to stop all use of your application, then the small status message is not enough feedback. If your status message has a vital message such as ‘Please Wait…’ it should appear in a modal window with a transparent overlay. This is clearly tells the user to wait, and users can be always more forgiving if they are aware of exactly what is happening.

6. Don’t Worry About Scrolling. Use It to Your Advantage.

Worrying too much about ‘the fold’ can seriously turn your user interface design from a scrollable, free flow design to a cramped and messy affair. The roots of the problem is an unrealistic fear that people who use computers do not know how to scroll or that anything under the fold will never be seen. What you need to combat ‘the fold’ is a quick way of explaining what your web app is all about above the fold. What is that? Why should users care about the design? Is there is more info further down the page? If you can be make your app interesting enough above the fold, users shall be scroll down to experience more of the page. Leave it enough content below the fold to continue to satisfy the user. Once if they’re at the bottom, you can be more fairly confident that you have an interested user looking at your content. The bottom of the page is most valuable area of your site because the end is mostly for users who are likely to engage with your app than casual browsers who stay mostly at the top.

No comments:

Post a Comment