5

The Android Design guidelines encourage '0-1 actions, not dismiss or cancel' for Snackbars (actionable toasts).

My question is about cases when a Snackbar is the best option to not interfere with the workflow, but there are two plausible actions users might want to take from the Snackbar. For instance, our Snackbar might look something like this. (Where VIEW would navigate to a feedback page, showing the consequences of the action)

mockup

download bmml source – Wireframes created with Balsamiq Mockups

Is this a definite no-no with regards to convention & guidelines, or is there wiggle room here?

4

It's not exactly a snackbar, but the google website uses a small popup with two links as call to action to download the native app. The two actions are clearly styled as primary and secondary and the touch targets are large.

Google mobile app popup

  • What is that dialog called? Or is that from the website? – Syakur Rahman Jun 19 '16 at 8:25
  • That's from the website. – Matt O'Keefe Jun 20 '16 at 11:18
  • From the design it is more similar to a banner. – Nash May 31 '18 at 7:55
1

Android is all about wiggle room

Of course, that's fodder for it's critics too. If your user needs two actions, given 'em two actions.

My concern in your example is the proximity of two fundamentally different actions. In mobile , you always have to consider the accidental tap with adjacent actions. Accidentally viewing when you wanted to undo would be an irritating experience.

If your user has a reasonably accessible path to view the change through the static UI, I'd cut it down to undo in the snackbar (which is an expected function there).

  • Great point about the proximity of the two actions. This raises the question for me, is the body of a snackbar ever actionable? Would it make sense to have an UNDO button, and have the VIEW action be called when tapping on the rest of the bar? Of course this would be completely pointless if that is not a common pattern. – Adam Thompson Nov 20 '15 at 23:04
  • 2
    It's not common. It could also be confused as an alternate way to trigger the undo. Seems hard to distinguish the two actions in that scenario. – plainclothes Nov 20 '15 at 23:08
1

I think this is a questionable design.

Snackbars should not require too much cognitive load from the user, since they typically disappear automatically or are otherwised dismissed quickly with a tap. Providing two options gives the user too much to think about in this limited time frame.

I already find it rather hairy to try to tap "undo" quickly enough, before the notification disappears, after I accidentally deleted an email in GMail. Providing two options would be panic-inducing.

The need to do this quickly will magnify the problem of proximity that plainclothes mentions.

Also, your particular design raises workflow issues, as well: what if I want to view an action then decide whether to undo it?

I'd say find another way to do this.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.