Tag Info

Hot answers tagged

3

Inline not Modal Inline edit is to be preferred at all times. The user keeps context, have the ability to use information related and narrow to the edit and the user don’t have to focus on a new UI. It is the same, simple, easy and straightforward process where the flow of work can be kept. Modal dialogue breaks the users’ context and it takes time for the ...


3

I'd go for: Option 3: Use a vertical ellipses to the right of the Call button that opens a flyout menu with two options: Edit and Delete. Mainly because this option is the one least likely to result in accidental deletes or unintentional entry to edit mode, but also because these are less common secondary actions but which still need to be ...


3

I think there are a few large considerations to keep in mind here: How big is the edit area (both in width and height)? If it is to be usable, it has to be very easy for users to see where it begins and where it ends, and easy for them to avoid accidentally scrolling outside of its view (for example, if a user is editing her profile and she accidentally ...


2

I would personally use an edit icon like the following This is your text By using an icon the users will know that there is an action associated with those contents, without having to interact with the mouse cursor. This solution works also on touch devices where the absence of a cursor would make it impossible to discover this functionality. I ...


1

From the interaction point of view People will be touching the UI a lot: long press, swipe, drag, double touch, etc. It can be frustrating to users if the renaming feature is constantly initiated because the user accidentally touched the screen.


1

Is this a form they use often or more like a one deal situation? Because if they see it once and will never or very seldom would see it again, just stick to form fields which are recognizable and present no usability threats, although at the expense of looking not so nice. If however, they use this often, and the pretty UI is a valid concern, why not have ...


1

You can add visibility or transparency property to your text element and manipulate it in most suitable way. For example: Add checkbox for each text element outside image so user need not to edit text to make it invisible. If user edit text and delete all symbols you can replace text in element with some placeholder text and set its visibility to false. ...


1

I think there are three big rules that must be taken in to account when identifying the best view/edit paradigm: I want the information to be easy to read (Summary/Print view without edit clutter) I want to prevent unwanted mistakes on important data I want to quickly and easily edit the information The UX solution for View/Edit may be different ...


1

I think it would make more sense to force the user to create the list first, rather than create the elements under it. You can name the CTA "Create a list" if none exists. Then, once at least one list exists, you can keep your "Create a new list" inside the drop down at the end like you did on your mockup. Then the "Add an element" could be called "Add a ...


1

One of the problems with using a double click or triple click is that they already have functions tied to them. A double click for example on text will select the full word, whereas a triple click will usually select all text in a paragraph or the identifying block (< li> etc..). The created dual interaction with the same input I think is very ...



Only top voted, non community-wiki answers of a minimum length are eligible