Hot answers tagged

101

Sudden rearrangement of content is disturbing Dynamically updating data while user is looking at it may (depending on type of data) be disturbing to the user workflow - for example, if you're reading a sentence and it changes while you're doing it, it's unwanted. The same applies for any content changes that will re-flow or reorder other content. Appending ...


28

I guess this should follow the classic usability guidelines for response time. 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result. 1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even ...


27

For Buttons I would strongly recommend looking at this excellent example which converts the button into an form submission indicator as well. Here are a couple more resources you might find interesting too which show relevant progress buttons Ladda Loda Buttons However if you are concerned about users trying to interact the button, you can always ...


17

In general, users expect links to link and command buttons to command. That is, links navigate, presenting new content without changing the underlying data objects or their relations or positions. Buttons change these things, performing creation, deletion, association, conversion, duplication, etc. An easy rule-of-thumb is if the most terse caption for the ...


17

Additionally, it's less data intensive, and if you're designing with a mobile first philosophy, that's got to be a consideration. You're going to need to consider that the screen size is constrained to smaller dimensions than a desktop machine, which means that even smaller changes are more likely to move what the user is looking at off screen. Many ...


12

You can disable the save button when there is nothing to be saved. You can also change its label from Save to Saved.


12

I've always been told that a delay of 100ms is generally not perceivable. An answer in a similar StackOverflow thread says: The 100 ms threshold was established over 30 yrs ago. See: Card, S. K., Robertson, G. G., and Mackinlay, J. D. (1991). The information visualizer: An information workspace. Proc. ACM CHI'91 Conf. (New Orleans, LA, 28 April-2 ...


10

Secondary rank If you have another factor that can rank the results (e.g. "popularity", "kuakeli rank"): start with the first letter limit results by second rank, by picking the TOP N (roughly: SELECT TOP 10 FROM Stuff WHERE Name LIKE "x*" ORDER BY Rank) If you don't have that rank, you could still start after the first letter, but results aren't as ...


10

It all depends on what your web application is supposed to do and how much of your site is changing on every page. if there's a small section of your site that's supposed to change, AJAX is your best option if a large piece of your site is changing (for example, only the navigation and footer are the same on all of your pages), then you should probably go ...


9

"1.0 second is about the limit for the user’s flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data." (See reference 2 below) I'd say, if a page needs more than ...


9

I like progress bars with stepped copy. download bmml source – Wireframes created with Balsamiq Mockups


9

Does the user need all the parts to be loaded to use the page effectively ? If so, then going with the approach of loading parts separately might not be a good experience as users might want to interact with these parts and find that they can only partially interact or not interact at all might ruin the user experience. However if you can interact with the ...


8

From a UX standpoint I think AJAX is going to be better 100% of the time IF you can provide ALL of the proper visual cues that the form is processing and not just giving the illusion of being broken. Some things to consider are: Provide a visual spinner within the <button>Submit <img src="spinner.gif"></button> and make sure to remove it ...


7

If for some reason there is an error, it might not be seen by someone moving really quickly through the control panel. To solve that, use frames in your website, so that there is a constant parent frame and 'top bar'. That can be a place for a loss-of-communication indicator. AJAX to the server can be made to go via that parent frame. This ...


7

There are some great ideas here for what to display during that 4 - 5 second period. But that period doesn't have to exist at all. The only thing that you really need to process immediately is the information that's going to be displayed on the next page load. Everything else can be offloaded to a background process. This approach would eliminate the need to ...


6

@Barfieldmvs response is probably the right way to go about it - show an "updating" state while the ajax call is in progress, and clear this when there is a successfull ( or failed ) response back. The advantage of this is that, should the ajax call die without any form of response, there is a clear indication that something is wrong, as the "updating" state ...


6

If you're halfway down a long page, say here on stackoverflow and friends, and the top of the page changes without disturbing your current viewport, how will you know? Yes, it could bring up a banner "we just refreshed the top of this page with three new items", but the notice "there are N posts you haven't seen yet" gives you a chance to interact with your ...


5

You can also use transitory status notification bars at the top of the screen. These would slide into view upon AJAX success, and then fade out after a very few seconds. These would also be anchored to the top edge of the window, as distinct from the top of the actual page itself. This means they'd still be visible even if the user had scrolled down the ...


5

IMO the first gives the best overall impression of UI responsiveness and understanding of the user's intent, (e.g., I've reconfigured the screen in anticipation to display the data you've requested). The second option could potentially be interpreted as something less favorable like Please wait while I figure out what exactly it is you want me to do. In ...


5

Pattern libraries are great for discovering how other people think about problems, and showcase their solutions. They won't always have results, but it'll be more effective than asking for examples on a UX Q&A site. A quick search on Dribbble: http://dribbble.com/tags/loading Here's an example result for Flight Tracker: ...


5

The answer is to validate in each tier so that you always ensure data integrity. This protects you against the scenario where any of the prior tier validations were skipped. I can't stand when developers build methods that assume the data has already be validated. Let's take the following scenario where your tiers are: Client Server Service Database ...


5

What you're trying to do is provide visual feedback that: the user clicked the button, you've received that click, and magic is happening to deliver the results. Disabling the button achieved the first two goals. The items Mervin lists off are good ways to achieve the third goal. The simplest response is disable the button after it has been clicked ...


5

The easy way If you're the one sending round the update notices each time, by far the simplest way to do it is to add a nice big 'Troubleshooting' section. The first thing you put in that goes: Why haven't I got the update? A: Try pressing F5 to refresh the page. However, there's not a 100% guarantee that users look at that, so you may also want to ...


4

After some discussion in the chat with @BenBrocka, it seems as if you've answered your own question. There's nothing about RIAs that distinguish them from normal user interaction, so any guidelines on good/simple UI Design should apply. The reason Android (and similar devices) have "best practices" specifically for them is twofold: 1) they use a different ...


4

Well I do agree that approach #3 seems the best option with regards to utilizing bandwidth and ensuring that the user has access to data at once, with regards to the other two choices I would recommend going for approach #1 since users like to switch between tabs to get related information quickly and a delay might cause them to lose track of their thought ...


4

I don't think enabling rearranging the menu items is worthwhile. There are many reasons why (I think) this isn't a good idea but 2 main ones are: 1) It's a feature that's not really necessary, so it enlarges the UI for not much return on investment (investment in design, implementation, documentation, and user learning). 2) It allows the user to lock ...


4

Don't waste user's time just because the visuals look good. 2 seconds is plenty of time to frustrate the user if it happens every time - and will make the site appear really slow because nothing appears to happen fast. It's important to provide feedback and confirmation of completion - but not to fake it like that. In any case, a lightbox is a distraction ...


4

Greeking is the generic term for showing fake text Greeking is a way to emphasize form over details. (Greek symbols aren't required) Lorem ipsum is probably the most familiar kind of greeked text. It allows looking at text formatting without actually having any content. Designers and developers often use lorem ipsum text to imitate real words with little ...


4

I've done it that way myself. My reasons were: If the login form had been just another view, then considerable information about how the app worked would be downloaded to the browser prior to log-in, making it visible to potential hackers. (Security was a major concern.) The security framework I was using had a convenient way to process login requests ...


3

The information should load as fast as possible. the important thing is while they are waiting for the real action you should give them some "loading..." sign so the user knows that the action worked. It's really annoying to click a link and not see anything happen.



Only top voted, non community-wiki answers of a minimum length are eligible