Earlier quoted context omitted.
What things? One seems highly unlikely, the other might be impossible. In on would have to be able to read complex human thought, in the other we would basically would have to predict the future.
My phone already suggests where I might want to go for dinner tonight. It's getting pretty good at it. Holiday suggestions don't seem that far beyond our capabilities.
Dropdowns Should Be the UI of Last Resort
101–110 of 241 posts
Re: Dropdowns Should Be the UI of Last Resort
#102On that note, is there a really basic caveman-friendly resource out there for UX-illiterate developers like me to help us make decent user experience decisions? A best practices text, or a guide for how to avoid the most obvious usability mishaps? I've had to "teach" myself most of this stuff by looking at other people's UX, but my results are still "meh" at best. Help! :)
Re: Dropdowns Should Be the UI of Last Resort
#103Earlier quoted context omitted.
Actually, in this particular case, I'd argue that this is incredibly relevant: Preacher preaches against UX sin. Commits UX sin with a non-zooming harlot.
No, it's not relevant at all. It's not a dumb rant against dropdowns: it's a well written piece with lots of examples and arguments that show which UX patterns are better than a dropdown for specific usecases. That's not preaching, it's explaining. Finding a small flaw in his site and using that to downplay the quality of the article and the competence of the author is shortsighted, rude and unfair. Nobody's perfect.…
It's orders of magnitude difference. Like, years to days. As in, maybe once or twice a year I get annoyed by a misplaced dropdown, whereas every couple of days I get annoyed by disabled zoom. One can make a solid critique of the wine at dinner but it's not irrelevant to point out the restaurant is on fire.
Re: Dropdowns Should Be the UI of Last Resort
#104I dislike the way mobile has become the new lowest common denominator for web development. It used to be IE6 because it was antiquated but now it's anything with a touch screen - mainly thinking how hover has been relegated to visual effects even though it's fine on non-touchscreens.
In the case of hover-based UIs is it more about common functionality? You can tap/click on both platforms, so is it easier to develop a single UI? One that uses the capabilities they have in common vs developing a unique interface for each device type?
Re: Dropdowns Should Be the UI of Last Resort
#105Earlier quoted context omitted.
Absolutely not. Disabling default zoom behavior is like hijacking the scroll bar - bad, ugly and puts users off. Also horrible is the tri state or undeterminate checkbox. All of the above are very trendy pieces of 'css and html codes' commonly found on popular DIY web dev sites. *edit: spelling
I do a lot of responsive design, and I turn zooming off So I CAN give you a proper responsive design that you can read and interact with on a small touchscreen. Why on earth would you prefer to pan around a desktop site designed for a big screen with a tiny cursor when you've got a tiny screen and a massive cursor (fingertip)?
I simply don't get the calculus, people who don't need to zoom won't and they get to see a nice site. What on earth do you win by preventing people that need to zoom from doing that? That they get to see a nice design that they can't use? And that is supposed to be better than seeing a usable site that needs panning? That's insane. I certainly hope your kind of thinking will go away quickly.
Re: Dropdowns Should Be the UI of Last Resort
#106I dislike the way mobile has become the new lowest common denominator for web development. It used to be IE6 because it was antiquated but now it's anything with a touch screen - mainly thinking how hover has been relegated to visual effects even though it's fine on non-touchscreens.
It's not about lowest common denominator. It's about what devices users are actually using to browse your site. If you make an awesome desktop version of the site at the expense of mobile, but majority are visiting on a small device, then you are alienating the majority. You have to keep perspective of why your are building something; if it is not for the users, then it is pointless.
Re: Dropdowns Should Be the UI of Last Resort
#107The advantage of dropdowns is their integration in the browser UI - which means stuff like VoiceOver works just fine.
I actually strongly agree here. If dropdown menus are so bad, then it's up to the user-agent to fix that. Remember that they're not actually elements, they're elements. If actions that require performing a can be implemented with a much better different UI for mobile or touch, then user agents are free (and encouraged) to do so.
Re: Dropdowns Should Be the UI of Last Resort
#108GUI's embody micromanagement as a virtue. GUI's in general should be a last resort. Computers are supposed to do our work automatically. Barring that, by delegation. Making rounded corners and gradients is easier than making something useful. that's why it gets so much attention. NoGUI.
I don't think it's a matter of last resort, rather correct use. GUIs are inevitable. You basically should only ask from the user what a computer can't possibly know, for example what date you want to travel for your holidays and how many units of that product do you want.
"What day do you want to travel?"
>
NoGUI.Re: Dropdowns Should Be the UI of Last Resort
#109Earlier quoted context omitted.
I do a lot of responsive design, and I turn zooming off So I CAN give you a proper responsive design that you can read and interact with on a small touchscreen. Why on earth would you prefer to pan around a desktop site designed for a big screen with a tiny cursor when you've got a tiny screen and a massive cursor (fingertip)?
How about giving me a proper responsive design, and then still letting me zoom in if your design sucks for me and the text is too small? Not everyone has the same eyesight or the same size phone.
The great part is, with recent support in CSS we can build one site and target desktop users and mobile users with entirely different hardware, and give them a unified experience and layout that's tailored to their device. When they use the desktop it's the same website, fit to their screen and ready to be used with a mouse and keyboard. When it's from a mobile device - all of the same information and actions are still there, just presented in a way that's intuitive and natural to users of a mobile device.
If you've ever used a mobile simulator on a computer you'll know how awkward it is to emulate the most natural and smooth fingertip gestures with a mouse. It's clunky! Well trying to pretend you're a desktop with a mouse when youve got a tiny screen and a big mouse (fingertip) is just as awkward and useless.
With zooming enabled, every tap you make takes 300ms longer to register because it's listening to see if that tap is a tap or going to be part of a zooming gesture.
I design my stuff to look good well beyond normal tolerances for screen sizes, and trust me - I am not your enemy here. I do what I do to give the best experience and if zooming ended with an easier-to-use experience then for sure I would enable it.
I do a lot of other things to make it easy for mobile users too:
- use tel inputs for numerical entry (mobile users get a keypad instead of a keyboard)
- user email inputs for emails and turn off autocapitlize (mobile users get a keyboard with an '@' symbol)
- use retina graphics, or render imagery in code for retina and pixel-dense displays
- every layout I create works from 300px-1500px, and some of the more important elements in the layout I may get working from 200px-2000px to be certain they will work everywhere.
- I use a massive wish-list of fonts that includes great defaults for OS X, Windows, Linux, Android, and iOS
- I use the least amount of JavaScript that makes sense to accomplish what I need to do (I hate sites that constantly crash the tab on mobile)
- I add offline and web-app tags according to the project to help users who may add the site to home screen have the best experience (not all sites are built for web app mod)
- I also add in special icons just for mobile users so if they bookmark the site they will have a nice icon as well
- I disable text-selection or pointer-events for items that may be errantly tapped on, or to help you be able to more easily select text you are trying to select on mobile. Text selection, copy, and paste on mobile is a magnitude more difficult than for a desktop user
So I'm not just disabling it because somebody told me to, or showed me that's how it's done. I work hard and develop, and use these devices, and building a desktop site you can pan around does not provide as good an experience as a properly designed responsive site.
I'm a mobile user too, trust me when I say I fight for your experience to be the best there is!
Re: Dropdowns Should Be the UI of Last Resort
#110Earlier quoted context omitted.
Absolutely not. Disabling default zoom behavior is like hijacking the scroll bar - bad, ugly and puts users off. Also horrible is the tri state or undeterminate checkbox. All of the above are very trendy pieces of 'css and html codes' commonly found on popular DIY web dev sites. *edit: spelling
I do a lot of responsive design, and I turn zooming off So I CAN give you a proper responsive design that you can read and interact with on a small touchscreen. Why on earth would you prefer to pan around a desktop site designed for a big screen with a tiny cursor when you've got a tiny screen and a massive cursor (fingertip)?