Hot answers tagged

170

I suggest displaying the button in its disabled state and adding a tooltip explaining why it is disabled and how users can get the permissions to use this action. Not displaying the button: Users will search for this option and will maybe think they don't see it and therefore may spend time looking for it, possibly refreshing the page, restarting the ...


65

From your description, I think the answer is pretty clear. I get your concerns about some users' expectations but this button shouldn't be shown for a few reasons. A disabled button will only generate negative cognitive load for everybody. Users will look at the button and think about what it does, how it's disabled, and how to enable it. You're saying ...


44

You should separate the two actions. Use tabs just for selection and for adding a task you should stick the action to bottom of visible area. Your tasks can be viewed by scrolling within the tabs and add action Here is the wire-frame of concept explained above.


28

Is user likely to be aware of functionality? Can an inexperienced user gain experience and then get the close privilege? If yes, hide the button. A button is extremely interactive element of a page. Consider these examples- In Facebook, if you open a post in which you can only share, like and comments option are not displayed at all. Even though one can ...


27

3 small action buttons on the left-hand side of each row With a LTR languages, one can assume users will first inspect the row (starting from the left) and only then decide to take action. So placing the buttons on the left side is somewhat counter-flow. 3 small action buttons on the right-hand side of each row Pros: Buttons are easily accessible. ...


24

I would choose option 3. Use arrows, but have the arrow pointing right when closed, and down when open. download bmml source – Wireframes created with Balsamiq Mockups The reason for this is that the arrow now always points to the content it relates to. If you have an arrow pointing up then it could be misinterpreted as pointing to the preceeding ...


24

Selection category and its action can be separate, as it likely to confuse most of the users. Having a clear separation between them will be more clear and it also standard practice for mobile. You may also want to consider any other actions that users might require on the screen and group them together. Have quickly modified the wireframe earlier shared by '...


23

Both are traditionally known for displaying More Options You can think of them as Ellipsis that refer to un-finished menu and hence clicking on it shows you the entire menu, finishing it. On Android, it is referred to as Overflow Menu On Apple and iOS devices it is referred to as More Options Menu Technically these are used to display Secondary options ...


19

Another way of doing this is by placing check boxes in front of every row and adding actions (Edit, Export, Delete) on single or multiple selection at the bottom but it really depends on the case. You can also have a top check box for selecting all rows in the table or on the current page (if you have pagination.)


17

The word New is generally used when you are adding something new to a existing list or creating a new list or object or account. So for example you might use New in conjunction with Create or add to highlight that an new entity is being added or created. As Samuel mentioned you might use Add to add an item to an exiting list or collection (example adding ...


13

Create. Use this word when you are about to make a new non-child record. On a listing window or page (we'll call it a view for convenience), there should be a "Create" link that will take the user to a new view where they get to enter all of the record's data. The new view should be entitled with the word Create, and the button to commit should be labeled "...


12

It's quite an age old question in UX/Universal Design. But, with time I feel the importance diminishing. Some reasons maybe true globalization of products/brands/english language/etc. I know companies still have to rebrand their products based on the country the are launching in, but those cases are getting fewer. Once again, just a personal observation. ...


12

I would use different visual indicators, and a secondary, like so: download bmml source – Wireframes created with Balsamiq Mockups The important thing is how often users will be selecting the actions... if they will 'Accept' 90% of the time, Reject 9%, and cancel 1%, then it's likely Accept should be larger/easier to hit than Reject, as shown above. ...


12

New in iOS 11 you can find the Floating Action Button within the Notes App. If Apple uses them, you could definitely use them too.


12

One massive reason for disabling (with explanation) the button rather than hiding it which has not been mentioned explicitly is that an experienced user will at some point end up using an inexperienced user's account alongside them. I commonly have a similar issue with a product we use internally that hides an admin button when being used by people with ...


11

You could proceed as follows: Try to reduce the width of the particular columns. This way you gain space. Move the contextmenu completely to the right, such that all actions are under one hood. Reconsider your actions. Prioritize and group them and correct the layout correspondingly. And in detail: Regarding 1.: For example, the column description doesn't ...


11

You have a primary and secondary action. Details is the primary action, delete is the secondary action. What you could do is move the delete function into the window that contains edit/information. This has the added advantage of cleaning up your listing layout. This will only work if delete is a fairly uncommon function and the use case is something like "...


10

Applications all over the place tend to rely on a color scheme that has already, to a certain extent, become a standard. Red means: Oh no! Careful! Beware! ATTENTION!!! Green means: Safe. Go for it. Ah yes, nothing to worry about. I don't think it slows a user down, quite the contrary actually. Since universally applications have adopted red and green to ...


10

TL;DR: I consider the Floating Action Button (FAB) to be the most polarizing element of Material Design, and generally wouldn't recommend a floating action button for use in an iOS application. The principle is still sound: provide a strong call-to-action element (CTA) to guide your users. Apple tends to favor the top-right interaction, but I consider the ...


10

System vs social In general use: Users report system problems. Users flag community problems. I'm not aware of any studies on the topic, so let's think about the terms semantically. When I encounter a problem with your system I want to send it over to be placed in a queue of issues. I want to "report" it. When I encounter something inappropriate, ...


9

It can be confusing to put something that is (that is the status) in a button that represents something that could be, (that is the action). Try to separate the Status and the Action (or button) into two clearly different elements, for example a text label and a button: download bmml source – Wireframes created with Balsamiq Mockups Then apply ...


9

Your actions are different: Edit is individual for each record in sense it starts another form for editing this particular record. Export and Delete are batch actions which could be made on a set of records. So Edit could be done by double-click and Export, Delete could be done using multiselection with checkboxes and single action button.


9

Given that you mentioned yourself that the user has already initiated the action, it is likely that the user will want to confirm the action. Cancel is not really an action, but rather a dismissal of the modal dialog. Given that, I suggest you strongly de-emphasize the cancel button. If you do, it becomes clear that you do not need the color coding in the ...


9

If you compare GMAIL user interface itself on the Apple and Android mobiles, the UI is a bit different (user pics and checkboxes - on the left-hand side, etc.). For the IOS, the GMAIL takes a different design pattern for FAB or button compared to the Android Design, but it still stands out. You may want to consider this design for your app. Frankly speaking,...


9

I would not ask the user if he's sure, i would assume he is and explain him his actions. I like invisions approach, they even added checkboxes so they make 100% sure that if you delete you delete because you want to delete and are 100% sure what this means. Of course for smaller actions or actions that get used frequently checkboxes could be annoying since ...


9

The main driving force should be user expectation. If the button is about a functionality that a user might expect to have, it should be there and the disabled state make it clear that it is not available (a hover tooltip can explain why). If, however, it is a functionality that the user with the reduced access rights would not expect to have or see (or ...


8

download [name of data] as [format] has many advantages. Here is why : Taking the user's perspective can help choosing between download and export : download is a word that focuses about the user's benefit because there is no ambiguity about the destination (the user's platform) and it will then be theirs. Moreover, virtually all Internet users have become ...


8

The answer is contextual (of course), but in general, you likely want to go with the simplest, most relevant text. In most cases, this means the well-understood 'Save' text is your best bet. If your button is placed in a context where there are multiple things to 'save' or where the context of what you are saving is otherwise unclear, then you could ...


7

Personally, I would make the UI different to compensate for their similarity. If they were both buttons, a user may accidently click on one than the other. Disable works well with toggles because it can be reversed. The delete action can be as simple as an icon or button. A trashcan or X is pretty universal.


7

Assuming that the reservation status always starts with being "Pending" - and is not a factor of user action, there are two distinct categories of system/user actions. First category has both confirmation and rejection. Changes reservation state and generates notification, Second category is deletion. Here I assume, only change in reservation state is ...


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