Android devs/designers, what do you think is the best approach the situation whereby a list requires* multiselection by default
A) Just allow multi selection by pressing, no need to long-press + CAB, get on with life.
B) Single selection via pressing, long-press to open a CAB and allow multi-selection. Enforce "the Android way", even if it's a bit retarded for a scenario where multiselection is the more expected (even more desirable) than single selection.
C) Single selection via pressing, long-press to multi-select but without CAB since there's no special actions applicable to a selected set in this case.
D) Other (please explain in comments).
Is my thinking that 'CAB should pretty-much-always come with multiselection' outdated? Material design guidelines for item-selection seem to indicate that (no mention of CAB), but the old long-press to activate multiselection reamains: https://www.google.com/design/spec/patterns/selection.html#selection-item-selection
Maybe only CAB if there's some special action applicable to a selected set of items? < seems wise to me.
On this one, as is too often the case, an end-client which is extremely iOS-oriented so I'll need ammo to backup any decision that isn't a near direct translation of the iOS UX. Long-press discovery is a big pain-point in getting the proper Android way across the line (i.e. non-Android Users struggle to appreciate the nuance), I've already implemented that in other areas of app where multi-selection isn't the main intention when interacting with a list.
*it doesn't have to, but it makes the most sense in terms of the data and the intention of the list in this specific case. #androiddesign #androidux #probablyshouldhavesetupapoll