👋🏼 Is there any example/code I can take a look at about

snackbars

and stacking them? Showing multiple snackbars in sequence, perhaps with different layout/color/text on them, actionable buttons, etc (the more complex the examples are, the better)

Please bear with my curiosity... is this something to be done at the UI side and not with orbit/view-model? Can you add a bit more context on what exactly we are planning to do here 🤔

No, I want to check how sending multiple events on the

sideEffect

which stacks (so the snackbar is not dismissed before another one is sent) works

I might be a bit late, but Google doesn't recommend the "side effect" pattern, instead in your case they'd recommend keeping a list of snack bars to show in your State and have the UI notify your the VM whenever one is displayed so it can be removed from the list

You’re not late! Appreciate the support, would you be able to provide a link to Google’s resource pointing this out?

Checkout the jetsnack sample, specifically the following files • https://github.com/android/compose-samples/blob/74b63c8c18c0eee5efcbc8d879681dea04[…]k/app/src/main/java/com/example/jetsnack/ui/JetsnackAppState.kt • https://github.com/android/compose-samples/blob/main/Jetsnack/app/src/main/java/com/example/jetsnack/model/SnackbarManager.kt • https://github.com/android/compose-samples/blob/4ae43c166b33ab82b3e4154e94e6576ec4[…]rc/main/java/com/example/jetsnack/ui/home/cart/CartViewModel.k

@Luca Nicoletti I think it was in that video Not sure though

Okay... Got it 👍

The fact that they're cached is also an issue, for example you might receive multiple snack bar effects at once, in which case you probably want them to be shown one after the other but with the side effect being sent as a Flow, you'll essentially show everything at once, or within a few milliseconds of each other. Ideally you'd want a buffer, which would be in your state if you don't use side effects There are ways around it, but it's just simpler not to use side effects and put everything in the state. I personally use them, but I understand why Google doesn't recommend them

I do agree with your points and the fact that we might need a buffer in these cases.

...but it's just simpler not to use side effects and put everything in the state

This is where I feel like something is off. For instance, in a large application with navigation that involves a backstack. Every time I receive a one-off event, after consuming these... and just before navigating to the next screen, I have to constantly remind myself to do the following 1. Clear my buffers (or mark the entries as consumed as and when it happens) 2. Mark any navigation events as consumed. 3. Reset other parameters that may repeat any strict one-off events.

I personally use them, but I understand why Google doesn't recommend them

Same here. Appreciate that you shared your thoughts here 🙏 PS: Here's a relevant thread in the pinned message section, for those who are reading through this and trying to grab some context.