You can think of Notifications as being analogous to abstract classes with mailables being one implementation of said abstract. Basically, you build notifications for a notifiable (i.e. a User). Then you can send messages to that user through any number of standard or custom channels - emails (aka mailables) being one such channel. If you only ever want to send emails, you can use mailables directly. If you want to be able to send to multiple channels (or dynamically decide among multiple channels), notifications are probably the better route.
@@Deadmanstrolln What I've been doing as of late is always opting for using a notification. My clients typically want their notifications via email, but we have an in-app notification bell that I can then use the toDatabase method for writing notifications for that. Thanks for the response!
@@kyledoesdev imo, if you're using laravel, you *should* be using notifications even if you only currently plan to send emails. That pattern lends its self to allowing the user to customize which notifications they want to receive, and future proofs you if you ever decide you want more than just emails.
Laravel makes sending an email so, so elegant and easy! Thank you!
Thank you for the efforts Jeff, Amazing explanation as usual
any benefit in using a Mailable as opposed to a Notification? Or is it personal preferance?
You can think of Notifications as being analogous to abstract classes with mailables being one implementation of said abstract.
Basically, you build notifications for a notifiable (i.e. a User). Then you can send messages to that user through any number of standard or custom channels - emails (aka mailables) being one such channel.
If you only ever want to send emails, you can use mailables directly. If you want to be able to send to multiple channels (or dynamically decide among multiple channels), notifications are probably the better route.
@@Deadmanstrolln What I've been doing as of late is always opting for using a notification. My clients typically want their notifications via email, but we have an in-app notification bell that I can then use the toDatabase method for writing notifications for that. Thanks for the response!
@@kyledoesdev imo, if you're using laravel, you *should* be using notifications even if you only currently plan to send emails. That pattern lends its self to allowing the user to customize which notifications they want to receive, and future proofs you if you ever decide you want more than just emails.
Great video as usual, any chnace of making a full ecoms in laravel? Thank you for your hard work.
We do have series for that on laracasts: laracasts.com/series/build-a-web-shop-from-a-z
❤❤❤
Thank u
Second
First
Second 😂
Great video as usual, any chnace of making a full ecoms in laravel? Thank you for your hard work.
We do have series for that on laracasts: laracasts.com/series/build-a-web-shop-from-a-z