2,259 reputation
38
bio website
location Buenos Aires, Argentina
age 69
visits member for 2 years, 1 month
seen Oct 15 at 17:19

User experience type with solid background in software development.
Always made people love the UIs I designed, encahced productivity in business appications.
Accepting remote gigs.


Oct
14
comment Should I avoid changing a “clunky” UI?
@Gutblender: before doing anything I'd check if this behavior is really annoying for the users, or it annoys me and only me.
Sep
9
comment Do people who are not power users open links in new tabs?
Also, it is not clear how to open a link in a new tab in an iPad or iPod's browser.
Apr
8
comment Is this rotating cube interface user-friendly?
I think the cube should rotate much faster, to give the user more opportunities to enter data. This would allow to add more fields to the form!
Mar
18
comment Next vs. Continue
"Next" is informative, while "Continue" is imperative. I try not to tell the users what to do so I'd use "Next".
Jan
28
comment Is the term 'field' too technical when giving messages on a form?
@Bart Gijssens: it is terminology from the 80-column card punch; a "field" was the term for several consecutive columns containing a single data item, like for example 6 cols containing a pre-Y2K date. The set of all fields is a "recod".
Dec
26
comment Should image overlays have a close button?
There are two use cases: 1- The user wants to play safe 2- The device doesn't have an "Esc" key (mobile) and touching somewhere else might trigger some other action.
Oct
29
comment What is the best way to deal with very complex forms?
There is another suggestion I recalled after my prior comments: in long forms it is very handy for the user to highlight the "current field", the one that has the focus. Browsers now apply an "outline" automatically, which can be configured. I also like to slightly change the background color. This helps the user to get back th where he was working after having looked somewhere else, his papers usually.
Oct
29
comment What is the best way to deal with very complex forms?
@Marcos: I'd like very much to see the outcome of your studies, even if they are in a language other then English.
Oct
23
comment What is the best way to deal with very complex forms?
Also, give the input fields sizes proportional to the size of the expected data. In addition to being a helpful hint, this breaks monotony and helps the to get back to the right point a user who turned her sight out of the screen usually to get a value from a paper. If a designer comes out with an all-same-size-inputs design don't kill him, but give him an warning he can't refuse :-)
Oct
23
comment What is the best way to deal with very complex forms?
The term "single column form" refers to forms having the labels on top of the input fields. You will be much better off with a "two column layout": labels before the inputs, in the same line. The single col layout has many problems for forms other than a login. Firstly, the forms end up being too tall, albeit with a lot on empty unused space to the right. Secondly, labels are displayed in small forms, which is an issue for users 45~50+ years old.
Oct
23
comment What is the best way to deal with very complex forms?
I'll add to the list the capability to automatically save partial results, like for example in the user's local storage. With lengthy forms it happens that a user could experiment a loss of her work due to the session end. It is convenient to ensure that the session is renewed at each user interaction, not only upon submit. You can use AJAX for this purpose.
Oct
23
comment What is the best way to deal with very complex forms?
@Marcos: "The framework does not support wizards" and "we can't do multipage forms" are independent facts. A few years ago I worked in a project involving 200+ fields forms, and after splitting them in pages the forms became usable.
Oct
8
comment Is a book more user friendly than an e-book?
@Majed: I'm working on a personal project to enhance on-screen reading, I say "making reading on-screen better than reading on paper". Have jotted down a lot of ideas so far, and I'm prototyping them. What's in your mind?
Sep
23
comment How Do I Avoid Users Becoming Numb to Warnings?
@Bulwersator: if might suffice with telling the user about the huge repo not being emailed before rather than after. And yes, hitting the delete trigger might have its cost.
Sep
17
comment How Do I Avoid Users Becoming Numb to Warnings?
@Bulwersator: yes I fully agree. But I thought that huge repos are not of the kind that is lost because of a single error because they are replicated in so many developers' computers. Tje issue is with the small repo of the single developer.
Sep
12
comment Are there any valid reasons for an application to steal focus?
@Tobias "that related question" (users becoming notification-blind) IMO is not about users but about the design of the notifications, the evaluation of what is important or not (regarding the user, not the application). Like what you said in your comment.
Sep
10
comment How Do I Avoid Users Becoming Numb to Warnings?
Anyway, a "anyway, the content of your repo was zipped & emailed to you" would be the extra mile in order to fully protect the users from their own errors (a.k.a. "making it fool proof" which I dislike because of the "fool" part). Kind of "undo".
Sep
3
comment Scrolling V Non Scrolling
The no-scrolling was fostered by Jakob Nielsen in an early alertbox article. Nothing was to be placed below the "fold". Years later he himself published another alertbox saying now that scrolling was OK, that the Internet population had learned about it. Show your client both alertboxes, so he can get the original version and the newer one (which, BTW, in not sooo new).
Sep
3
comment Is a middle dot (·) the best way to signify a space?
When something has to be explained too much, and makes a FAQ, then it's time to revise the need to to is that way and to think of a better one, one not needing the user to know extra information.
Sep
3
comment Desktop metaphor - Why is it called “windows”?
As @user1757436 said, there were windows before Windows. For us developers a "window" is a rectangle capable of displaying content and with a set of properties and behaviors, bah, an object. MS seized the word. A few years ago they almost lost a case against a small company using the name "Lindows" (Linux + Windows). They settled giving Lindows a lot of money to change their name, because by the USA law a company can't register as a brand a common word.