116 reputation
6
bio website
location
age
visits member for 2 years, 2 months
seen Jul 14 at 13:47

Aug
18
awarded  Popular Question
Feb
12
awarded  Commentator
Feb
12
comment When client and server side validations occur, doesn't it make for a better UX to only do server validations?
Here are the results of a study about different forms of inline validation: alistapart.com/articles/inline-validation-in-web-forms And here's another interesting article about inline validation in general: uxdesign.smashingmagazine.com/2012/06/27/… Maybe it's helpful...
Feb
12
comment When client and server side validations occur, doesn't it make for a better UX to only do server validations?
For the user the best option would be validation on lost focus for every single input element - it doesn't matter whether this technically happens on the server or on the client side.
Jan
9
awarded  Supporter
Dec
7
comment placement of interaction elements on screen?
In our application we have actions that are related to the list or a single list item. So everything a user does has an effect on the current screen. And we have actions that are for navigation only and that lead to another screen. However, we also have actions that refer to a list item AND navigate to another screen (which means the user starts a new task based on the selected list item). I think it's important to differentiate (also visually) between actions that make the user stay in the current task and actions that lead to another task (=screen).
Dec
4
awarded  Nice Question
Dec
4
comment Should the order of add / edit / delete buttons be based on the frequency of their use?
Thanks for your answer - in this case it's not my intention to guide the user's behaviour (in terms of manipulating). It just needs to be very obvious what can be done on a screen, although the aims a user wants to achieve on a certain screen can vary depending on the current use case. (It's a software for doctors that need to use it everyday, so it's more about getting things done quickly.)
Dec
4
asked Should the order of add / edit / delete buttons be based on the frequency of their use?
Dec
3
revised placement of interaction elements on screen?
added 425 characters in body
Dec
3
comment placement of interaction elements on screen?
Also the possibility of multiple delete will depend on the kind of list. The group items are just tab items that open another list/view...
Dec
3
comment placement of interaction elements on screen?
If possible we will keep the options always visible, there will be some special lists where not all items are deletable, for these special items we will set the button disabled.
Dec
3
comment placement of interaction elements on screen?
The list could be a list of health insurance funds or a list of patients or a list of doctors or a list of users or a list of pharmaceuticals... Very different entities and for each entity the user needs to be able to perform very different actions...
Dec
3
comment placement of interaction elements on screen?
I agree, this solution would be very nice and clear if we had only 3 options (edit, delete, add). Problem is how to handle different tasks, e.g. 'create a new order for item1' which refer to a list item. There could be many of these tasks an i think that it wouldn't fit at all or at least look very crowded if we placed every option on each item in the list...
Dec
3
comment placement of interaction elements on screen?
OK, I see your point. The problem is that what looks like a navigation only element (the 'go to XYZ button') could also be an action that refers to a list item, e.g. 'create a new order for item1'. This action would use the data of item1 to open a new screen for creating an order.
Dec
3
asked placement of interaction elements on screen?
Oct
19
comment Same or different visualisation for validation errors and concurrency errors?
Thanks a lot for your answer. This is what my gut feeling told me, but I was not able to make a good case for this solution. Your reasoning helps me out and just makes perfect sense.
Oct
19
awarded  Editor
Oct
19
revised Same or different visualisation for validation errors and concurrency errors?
added 573 characters in body
Oct
18
awarded  Student