Timeline for What are the effects of breaking typical question order in web forms?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2012 at 2:30 | comment | added | Formulate Information Design | Of course design is user experience. My point was that we should be looking for a design that works, not one that hides problems. | |
| Apr 30, 2012 at 13:40 | comment | added | Niki Tonsky | @FormulateInformationDesign sorry, but design is user experience too tobiasahlin.com/blog/skeumorphism-and-storytelling | |
| Apr 30, 2012 at 2:10 | comment | added | Formulate Information Design | If (to paraphrase) we are "hoping the effect of untraditional form presentation will hide problems", we are not practicing user experience very well. Our job is to create designs that require less effort from users, not more. Moreover, people don't care about the form, and will not attend more carefully to it just because it seems "less boring". All they want to do it get through it to access whatever product or service is on the other side. | |
| Apr 28, 2012 at 16:17 | comment | added | Myrddin Emrys | I disagree about the repeat password; the number of typos you get with a hidden field like that are immense, in excess of 7% in my tests. You do NOT want to re-send a big chunk of new users through password recovery; they will just abandon. | |
| Apr 28, 2012 at 16:14 | history | answered | Niki Tonsky | CC BY-SA 3.0 |