Tag Info

New answers tagged

1

I like a modal window for "interruption" tasks. That is, tasks that are performed when you're really trying to do something else. Signing in is a good example. From any page I can click to sign in, complete the little form, and get back to my current task. Granted, that can be done without a modal (when Sign In is on its own page, submitting can jump you ...


1

An interesting way of using does "context of use matter" I guess? The answer is "yes, it does", and you can get a good overview of such variables on the web, starting perhaps with the NIST CISUR document (Level 1) which covers different aspects of context as illustration. Common Industry Specification for Usability - Requirements ...


1

Modals are a popular for a good reason: They provide fast, focused, contextual interaction. Page loads should be saved for when they're really needed to move the flow forward. Another contextual information option is content that loads into the page as needed. I've used this solution for payment forms in particular in the past. This article reminds us of ...


0

2012 from the NY Times These days, even 400 milliseconds — literally the blink of an eye — is too long, as Google engineers have discovered. To test page load speeds and optimize settings for best performance, you can visit Google Page Speed.


1

Why do you need the delay? As long as the search text field is constantly available, you could start the search after the first key is pressed, and refine it on each successive keystroke. Take Google search for example: After the first keystroke, the search starts: No results yet... ...Finally the results appear:


1

I ran into a similar issue with an auto-complete we were working on some time back where I was typing and I never saw the results until I was done typing but another colleague saw it while he was typing because his pauses between typing caused the backend calls to get triggered. There is really no silver-bullet here but I figure a 1000 milliseconds delay is ...


4

That really depends on the users and on what they are typing. Typing on a physical keyboard is significantly faster than on a touch device. So the question then is what the average WPM typing speed of the average user on your system is, and then work backwards from there. Let's say that it is 25 WPM. Typically a word is considered 5 characters long, so ...


2

Rather than a consensus on a static delay, maybe you could look into something a bit more adaptive. For example, if it is rare that a search will be for anything shorter than a few words or a few characters, try to determine the user's words-per-minute rate, or characters-per-second. Once you have these you can trigger a search when there is a significant ...



Top 50 recent answers are included