20,449 reputation
2859
bio website
location
age
visits member for 3 years, 7 months
seen yesterday

Apr
4
comment Help bubble next to a radio button
Option 3 might be OK, but you'll want to ensure you run it through a screen reader to ensure you have the source order correct. It may not make sense to have the help read to you before the item the help is actually referring to.
Apr
4
comment Help bubble next to a radio button
Option one is the only viable one, IMHO. Proximity is correct, and you're not interfering with the label/input relationship. @darklord Note that the last option won't work on a touch device and it also offers no context to the user that there is help to be found.
Apr
4
comment Why we don't use wider interfaces on wide screens
@danijar no, 320px would be the smallest common resolution. :)
Apr
4
comment If I am not the developer and I haven't hired one, how should I explain the development step of my UX design process to potential clients?
In general, if you are solely focused on UX, it'd be better to adopt a 'we partner with...' model for things outside of UX. So partner with developers from day 1. Partner with visual designers from day 1. Partner with marketing, etc...
Apr
4
comment If I am not the developer and I haven't hired one, how should I explain the development step of my UX design process to potential clients?
It sounds like you focus on UX Design (which is great) but gloss over visual design (which isn't so great--per the feedback you got). I'd just omit saying anything about 'themes'
Apr
4
comment Should I add sound effects to my web site?
@ChristopherJamesCalo perhaps partly, but while there certainly is poor sound implementation there are also very objective reasons as to why sounds should be avoided in general on web pages. Yes, there are rare exceptions where it can be a nice thing (one example being when used very sparingly as a background alert)
Apr
4
comment Why do users reply to messages clearly marked as do not reply
@Pdxd who's to say? I can't speak for each user. But email, as a medium, is designed to be a two-way street. I'd suggest that emails sent from a no-reply address are akin to robo-calls on your phone. They're impersonal. Sometimes that's fine, but for those that do want to reply, why not let them?
Apr
3
comment Designing For Big Screens / TVs Best Practices
For sure. You'll have to weigh the readability of the font size with the time it takes to show the pertinent data to the user.
Apr
3
comment Why do users reply to messages clearly marked as do not reply
A better question: Why are emails sent that aren't designed to have responses to? :)
Apr
3
answered Designing For Big Screens / TVs Best Practices
Apr
3
comment Designing For Big Screens / TVs Best Practices
This sounds less like 'web design' and more about 'kiosk' or 'wayfinding/signage' design. Perhaps use those as your search terms.
Apr
3
asked Research/Data on mobile interactions vs. desktop forms?
Apr
3
comment Why do squares look taller than wide on screens?
If you draw a circle on screen, is it a circle? If not, it sounds like your screen is set to a resolution that doesn't match the aspect ration of your monitor.
Apr
2
comment How can I show popovers on a mobile browser layout?
That's certainly an option.
Apr
2
answered How can I show popovers on a mobile browser layout?
Apr
2
comment What kind of text editor should I use for a reddit-like website?
I'd use the one right here on StackOverflow. To me, at least, it hits the right balance of 'just enough tools to be useful but not so many as to be annoying'
Apr
2
answered Usage of mouse click or replacing with hover
Apr
2
comment Where to place call to action on the iOS mobile form?
(also: can you customize the button on the keyboard? I wasn't aware that you could.)
Apr
2
comment Where to place call to action on the iOS mobile form?
I don't know that I'd use the term 'call to action' for that. The action is the page itself...fill out the form. The 'call' to action should have happened before the user gets to this page.
Apr
2
comment Preparing Positioning Specs for iOS Developers
You can't. If the developers don't have an eye for detail, no amount of documentation will fix it. Try to adopt a more agile process with plenty of feedback loops so you have the opportunity to review multiple times before going live.