Snackbar, Toast & Dialog in Flutter (Flash Package)

📗 Learn from the written tutorial 👇👇
resocoder.com/...
📧 Get Flutter news 📰 and resources:
👉 flutter.education
👨‍💻 Do you write good code? Find out now!
resocoder.com/...
Snackbars and toasts are the most used ways of notifying users about something within an app. The problem is that snackbars are not very modifiable and toasts, coming from native Android, are not even present in Flutter by default.
Flash is a highly customizable, powerful and easy-to-use alerting package for Flutter. It offers snackbars, toasts and even dialogs so that you can manage everything using just one API.
Go to my website for more information, code examples, and articles:
● resocoder.com
Follow me on social media:
● / resocoder
● / resocoder
● / resocoder

[@alexandrufilipescu1301]

Thanks! Hey Matt, I think that the people would like to see a tutorial on how you build your own apps or freelance, like the usual way that you do.

[@JuanLopez-oc9yv]

Thank you for sharing all of this, with every video of yours I discover new and more efficient way to do things with Flutter.

[@pedrol4011]

Thank you so much Reso! You are the best!

[@urielaispuro2125]

Awesome! I just found your channel and you're incredible, thank you for sharing your knowledge ♥️

[@h3w45]

Thanks for covering this.

[@raulmabe4229]

Hey I love your videos! You do a great work. However I think that snackbars are customizable by default. As everything is a widget you can insert a Row inside the content of a snackbar for example

[@prajwalc5595]

Thanks a ton man!! BTW I watched your entire series on TDD and Clean Architecture, It's a masterpiece out there on the internet. I have a question though, who should do the orchestration if a user action has to deal with more than one usecase? For example when a user hit a button I will have to make two API calls that is in two different repositories. In such a case what should be the approach? Should I create a single usecase that takes in two repositories and do the orchestration within the usecase OR should I create two usecases seperately and orchestrate the api calls sequentially in the bloc? Any feedback will be really helpful.

[@rifqibyy]

this is awesome, thanks! can you do bottom navigation?

[@kikalamuofficial5865]

Is this package still useful even when using Bloc Pattern?

[@mehulbisht9708]

So will you make tutorials on Flutter Web as well? It's not out of beta yet, but do you think it can be used to build websites for commercial use as well?

[@markusandrew8360]

A tip: watch movies on Kaldrostream. Been using it for watching a lot of movies during the lockdown.

[@seangerardo66]

@Markus Andrew yea, been using kaldrostream for months myself =)

[@daxtonjohan3020]

@Markus Andrew yea, I have been watching on kaldroStream for months myself :)

[@ramonjack6784]

@Markus Andrew yea, been using kaldroStream for since november myself :D

[@HH-uw3kw]

What theme are u using ??

[@merickbao4033]

could you please tell us about your vscode theme.

[@aytunch]

Matej, Hi thanks for bringing this package in to light. I have a question.
I made a nice small custom widget which shows some live data from the server. I want to persist this widget on top of everything else just like a toast. I don't want it to disappear when we do pop route, push route, etc. Can I use this library for this need?
If yes, should I create this widget with the toast above material app? Do I always need to pass the context? Or how should I go? I am using Blocs as state management. I always wanted to show a toast like widget from bloc instead of UI-bloclistener. Because it can appear at any random page, I dont want to put bloc listener to every page just for this purpose.
Lastly, does using Overlay and OverlayEntries have a negative impact on UI performance? Should we avoid them in our designs when possible? I think overlay's live in a different place than the normal widget tree.
Take care bro.

[@ResoCoder]

You could use this library but I'd recommend you to use the Overlay widget which is used behind the scenes here.
In fact, you might want to take a look at the flutter_portal package. It makes working with overlays much easier.
Overlays don't have any real negative impact on the performance. They are really just a stack of widgets that usually wraps the whole MaterialApp - that's why individual OverlayEntries are shown above the whole app no matter where you navigate.

[@thevillageguy321]

Thanks for neat and clean tutorial. What's the font you are using. IBM Plex?

[@ResoCoder]

You're welcome! The font is Jetbrains Mono.

[@numanarif2597]

Awesome man, thanks

[@ResoCoder]

Glad to help!

[@namtranquang8081]

What font is that?

[@GabrielCosta-xr5vr]

Missing more advanced content, but thank you for sharing this too!

[@ResoCoder]

Advanced content will come at some point!

[@ngocnghiale5717]

I don't want to use Overlay so I have a way to replace it:
//!Code
FlashController? flashController; //!Edit 1
showFlash(
context: context,
onWillPop: () async {
flashController!.dismiss(); //!Edit 2
return false; //True with Toast
},
builder: (context, controller) {
flashController = controller; //!Edit 3
return Flash.dialog(//!Your code);
},);

[@berkcan3475]

its sooo stupid IMO, let me give an example: I want to make user log in, while user is logging in I want to show snackbar not dismissable not with ability to go back, if I use persistent:true it can dismiss via back button, if I use persistent:false then it can go previous screen via back button isnt there any dev maintaining this repo smart enough to make a back button handler instead of choose one of shitty paths ???