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 ...


67

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.


29

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 ...


28

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. ...


25

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 ...


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 '...


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 ...


15

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.


14

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

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 ...


12

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 ...


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 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

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

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 ...


6

download bmml source – Wireframes created with Balsamiq Mockups I might suggest putting the "Unverify" action into the context of each row, so that it's clearer that "Verify" is the primary action, and also to avoid accidental Unverifications.


6

It is best to give some sort of feedback. The Netflix DVD Queue doesn't pop anything up, but it gives clear visual feedback that something has happened and that you can undo it. Gmail provides an actual popup, but it's completely ignorable. The problem with modal popup notifications is that stopping what you're doing in order to close notifications - that'...


6

By removing the icon, you can separate viewing from modifying a record. You also reduce ambiguity from icon interpretation. Since a common use of a list is to access a record and view its details, you could keep the actions as 'actions' which you have as specifically editing and deleting a record. Try to remove ambiguity If it's obvious that you can select ...


6

Yes, remove the dialog box altogether. Users are conditioned to not read them. Take them directly to the results page with proper pagination (loading a few results per page). If they need finer control over results shown, provide the dropdown option to choose how many results per page to load.


4

If you go with a two-click confirmation process, you should ensure the design can't be tripped by a double-click. Worse would be if in the design a double-click could result in either a confirm-confirm or a confirm-cancel, depending on which end of the button they double-click. One way would of course be the second approach you mentioned, that of "using a ...


4

In terms of the order, the primary (in terms of user association) identifier for the data row should always be on the left in a left to right language localization. Note that if you have a unique ID for each item, this may not be appropriate if it's not what a user themselves would primarily associate with that item, or the main feature they would generally ...


4

Never have one icon for two different actions. This will confuse the user. Always use a label with the icon to make the icon and action clear. A user’s understanding of an icon is based on previous experience. Due to the absence of a standard usage for most icons, text labels are necessary to communicate the meaning and reduce ambiguity. Source: ...


4

Try separating a multistep action (booking flow) from an immediate one (calling) with explicit actions. In this case, one path leads to an immediate (desired?) interruption for the staff: You're calling them. The other path is a booking. I'm assuming there's a separate, at least 1 step path to completion. Tradeoffs The extra buttons do add more visual ...


3

1) 'Archive' actually will be misleading unless record retrieval is provided. 2) 'Hide' is also not appropriate, since 'Show' is the opposite of Hide and user may think that there is an opposite action somewhere else. Hence either go with 'Dismiss' and 'Delete' or, I will feel more appropriate word is 'Ignore' and 'Delete'. By clicking 'Ignore' user is ...


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