@zkat The problem with the flash implementation is that it is misused as grab-all for all kinds of messages.

It should definitely not be used as a method to show an error message as result of user interaction, because the message is disconnected to the user’s actions. It does not support screen readers because it can’t point to the errored field id. For system wide error messages it can have its place, such as connection errors.

Success messages like “welcome back” and “resource created” are redundant and lead to alert fatigue.

It is possible to render the flash message on the page, instead of using the flash/growl UI, which I’ve done on a LiveView user login form.