I am working on designing an inventory management system. I feel one design is closer to optimal but I need a sanity check on this. I won't say which is mine and which is not.
The debate is whether to put the actions on each list item, hidden in an ellipsis icon, or at the top of the menu where they can be assigned with checkboxes.
Which design is better? Is there a third way?
Ultimately this comes down to the user's need in the given work environment. Inventory systems are built to allow the user to work with maximum efficiency across a variety of job related tasks. In my experience users of these systems often deal with processing hundreds, even thousands, of records. Some need to be processed in mass.
That said, if the user needs access to batch actions, that is to apply a request across multiple records simultaneously, then select the first option. Otherwise select the second.
If you would like to further reduce the ui footprint and promote discoverability, for the first option, you could consider rolling the individual actions up into a single drop down button in a table toolbar. Or you could employ a floating toolbar to support Fitts law. This toolbar, containing the actions, would become sticky as the user scrolled down. Also, I would add a check box in the column above all the other selections. This would act as a select all feature, selecting all records currently displayed.
Easy.
First up. The Overflow icon at the right of each icon, isn't the best design approach you could take, since if it's a long list, it might mean to select each of them individually.
Second, There is a possibility that the user accidently selects the overflow icon of the wrong list view item and performs a negative action onto it.
The approach I would recommend taking is Design 1.
However, here are a few modifications I would make.
Instead of keeping the Checkbox visible at all times, I would recommend to keep it hidden and only visible on a Selection activity (say long-press or double-click, dependent on the platform and key mappings.)
As soon as the user selects one item, a Checkbox appears with a Tick against that item. Now he can perform any of the Actions.
Also, Design 1 is universally accepted as it is.
In terms of clicks both design takes 2 click to perform an action. If the requirement demands user to performs bulk action (like performing action for multiple record) then Design 1 suits better.
I believe best practice is to bring the action as close to the object as possible, for multiple reasons, including: 1) Action is in the right context (less ambiguity as to what the actions apply to, etc..) 2) less movement required (don't have to go back and forth between top and middle of the page.
That being said, it breaks if you want to allow multiple selections and actions on those.
