If I am honest, the main reason I use toasts at first is because it ensures mobile compatibility. The problems with mobile UI (dismiss X offscreen, feedback off screen, user refreshed the SPA app page ruining state etc) are less likely to occur with a toast. They also bring some element of tolerable, expected animation (like 'page loader bars') which newbies often miss, and make the experience less jarring as a result.
Yes it's not great UX but it functions consistently well. Although 80% of the applications we use day-to-day may be by big corps with excellent UX and time to spend on it, 80% of applications built never get round to even consistent and fairly error-free UX. So I consider reaching that stage more important that adhering to a beautiful, but more risky, cross-platform UX strategy when in early stages with limited resources.
Yes it's not great UX but it functions consistently well. Although 80% of the applications we use day-to-day may be by big corps with excellent UX and time to spend on it, 80% of applications built never get round to even consistent and fairly error-free UX. So I consider reaching that stage more important that adhering to a beautiful, but more risky, cross-platform UX strategy when in early stages with limited resources.