Reputation
1,058
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
4 15
Newest
 Pundit
Impact
~12k people reached

May
13
comment Should I show the “Save” button before the required state is achieved
+1 there are so many frustrating times I've had to angrily google "Why is [x] greyed out in [application]" or "Why has the [x] button disappeared in [application]", and it always takes a very long time to find out.
Apr
27
comment Should I redirect the user if there's only one search result, or still show the results list?
The new Google Maps is an interesting example that is on the edge for this. If I search for, say, "Washington Monument", there's only one such place, and I expect to be taken straight there, not given a list (which is what it does). But often it gets it wrong: e.g. recently I was searching for pubs with gardens, but instead of giving me a list, no matter what I typed just took me to one nearby pub called "The Garden". If you make assumptions about users' intentions, give them an alternative in case your formula guesses wrong
Apr
14
awarded  Pundit
Apr
14
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
Downvotes on SE are broken, 90% are just meaningless animalistic grunts from the ignorant. I stopped caring about downvotes years ago, sadly. This is the best answer, so have an accept.
Apr
14
accepted Are there devices narrower than 320px (and data on their usage for web browsing)?
Apr
13
answered Back button on iPhone
Apr
13
comment Why is it important to focus on user needs as opposed to requests?
How about: at the time the iPhone came out, everyone was asking for smaller phones plus netbooks. You can't request something you haven't seen yet.
Apr
8
comment How to display zero percent of progress?
Haven't heard "very 2.0" for years... Five greyed-out ticks, turning green when done, is another option, or circles with ticks appearing in them (I'd avoid squares since they'd look like clickable checkboxes)
Apr
7
answered Slow down job for better progress animation
Apr
7
comment Slow down job for better progress animation
This is a good approach (+1) but only if there's no pressing need to allow users to abort a process. If those subtasks are "Prepare missiles", "Arm missiles", "Launch missiles", don't give if the impression they haven't yet completed when they have!
Mar
23
comment How to indicate that an element is “new” in a list
It's possible to have the fade only begin when the tab gains focus - but it's still worth reconsidering since you're unlikely to know which list items are on the page and which aren't yet scrolled down to (of course, you could check for that too...)
Mar
23
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
The most recent moderately popular Android phone I can find with less than 320px width was the original Samsung Galaxy Mini, from early 2011. That's 240px x 320px, so even a user with an exceptionally small 4 year old phone can still use a site with a minimum of 320px+, with an imperfect but usable choice between landscape orientation or side scrolling.
Mar
13
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
Well, no, not if only looking at existing users is not an option for any of the three reasons outlined in the question. And assumptions like "I think 320px is narrow, so I'm going to guess that no-one uses devices smaller than that for the web" is exactly the kind of attitude I'm looking to get away from. I'm looking for real evidence about real web users in 2015.
Mar
12
revised Are there devices narrower than 320px (and data on their usage for web browsing)?
edited title
Mar
12
comment What is the smallest screen size you design for
I've asked it as a seperate question: ux.stackexchange.com/questions/74798/…
Mar
12
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
Good question. It'd depend on the usage stats - if a substantial number of people use it regularly to browse the web, I don't care if it's a watch, phone, games console, toaster or fridge. If there's no evidence it's common or commonly used for web browsing, it goes in the 'unsupported' bin alongside old-school feature phones and early Blackberrys.
Mar
12
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
Nice, +1. Sorting by most recent first, it looks like the most recent <320 is the Nokia Asha 302 from March 2012, at 314px wide, using Nokia's now-defunct proprietary OS. Even the Samsung Galaxy Mini 2 was 320px wide. I have to go back to 2011 for anything <310px. Compelling argument!
Mar
12
comment Are there devices narrower than 320px (and data on their usage for web browsing)?
What do you mean by "Today (and I insist on that) you don't want to read a full article on a 320px wide device"? I don't understand that phrase. And yes, I don't care if the <320px device is a mobile, tiny tablet, tiny laptop, toaster... just whether it and its web browser are in widespread use.
Mar
12
awarded  Yearling
Mar
12
asked Are there devices narrower than 320px (and data on their usage for web browsing)?