1. Declare a "global"

TextSnackBar

and expose its state via `CompositionLocalProvider`: I can show any message anytime I want to with ease, but achieving custom style/behavior is hard. 2. Declare a "local" `TextSnackBar`: each screen has its own

TextSnackbarState

that can be used to display different messages: more code, more nesting, avoids global state but achieving custom style/behavior is hard too. 3. Declare as many

TextSnackBar

I need in each screen: if I have two different messages, I need two

TextSnackBar

with their own

TextSnackBarState

. More code, same nesting as 2), custom style/behavior is easy to do.

Well, at the moment I don't need custom behaviors nor styles, so I opted for 1). However I don't know if it's a bad idea