Tag Info

New answers tagged

1

A commonly used pattern to skip a displayed number of pictures is pagination. Pagination solves a few UX problems commonly associated with skipping content: A reference point is needed. (Where am I now?) How do I get where I need to go (Where do I go?) On Mobile/Table devices it's important to limit the use of the keyboard when using navigational ...


1

Design the entire interaction, not just the label If the interaction is for the user to enter an image number in the box, then the interaction must include clear labeling for the images so the user understands what entering an image number means. For example: Here, the images are clearly numbered so it makes little difference whether the caption reads ...


0

Jump to image #: View image #: Similar in phrasing to jump to page, which many users will be familiar with.


0

First we should know what is the goal. You might want to encourage the user to fill in his profile but it's not the only posible case, either ways don't show empty fields to visitors. If it's beneficial only for the user but not you to fill it in, that case hide the empty fields in profile view and only show on edit page.


1

Well, if the fields are optional, then you're offering the user the option to NOT to fill some info. As a result, you have a zero data field. In this case, you face the issue of how to handle this. While Adit Gupta's links are really nice and informative (and I recommend you to check them out for ideas, as well as this one), your case is very different. ...


0

I think one of the best ways to handle it is to provide a delightful message to the user along with encouraging him to take the next step. This article on Tympanus can give some more clarity on how to handle empty states. Also, check out this interesting page showcasing how apps and websites handle empty states - Empty States


0

I would suggest to include (y/n) in the question itself, like this: Do you wear glasses? (y/n): If user enters a wrong answer, just display back the same question again. I believe this will be self-explanatory: Do you wear glasses? (y/n):5 Do you wear glasses? (y/n): .. What's your height? (cm):172


0

I agree with Paul. If you have chosen CLI, then I guess your users understand what should be entered. But manual or typo errors will occur. Humans make mistakes. Even for boolean inputs "yes" may not be accepted in place of "y". This scenario can extend to integers as well, where user might type a comma instead of a dot. The UI should let the user handle ...


1

It's not recommendable to use the word Cancel in pop-up/alert boxes. You could use another wording like close or quit. You have several good combinations for the buttons, here is just one (for example, you could change Cancel for "No, stay"): download bmml source – Wireframes created with Balsamiq Mockups In the case you decide to use it, you ...



Top 50 recent answers are included