Hot answers tagged design-patterns
You can simple use "actions" button which opens on click all available action for specific row. Example:
Great question! This is a very common design pattern and it's one that sites screw up all the time (IMO!). Usually the objective is: Ensure the user sees the notification. Allow the user to get on with using the site smoothly after that. Don't p*ss off your users. This seems simple, but implementations often break the objectives! For example: Model ...
Here's a rule of thumb on data tables. For people who read from left to right, you assign priority from left to right because that's how they read. (Note: it'll be reverse for right to left languages e.g. Arabic) Columns used for ID & scanning gets higher priority Because we read and scan information using the "F-pattern", you want the identifying ...
Where should the delete option be? I see many examples placing the delete icon or text on the far-right of the row. Is this best practice? Is it always advisable to swap row delete to checkbox selection/batch delete? I believe the far right location is because you don't want user to accidentally click on delete. It depends. For a really long (tall) ...
It does sound like a tree. The most obvious form will probably look like the following (option 1): It can be optimized a bit (option 2): Or simplified (option 3): Does any of these options look suitable?
Tabs indicate that there are different views of related information that can be swapped between at any time. Showing tabs and not allowing them to be used adds cognitive friction. I wouldn't show the tabs at all until after a selection is made on the first screen. Be sure to keep the first screen as simple as possible and only ask for the minimum amount ...
Only top voted, non community-wiki answers of a minimum length are eligible