Dennis H. Lewis explains why backend workflows matter in Bubble: they run on the server independent of the user's device, making apps more responsive and reliable. Client-side workflows still work for immediate UI changes, but backend workflows are the mark of professional practice.
Chapters
Can you talk a little bit about the difference between front end workflows and backend workflows? Because I feel like that's also.
A main key point where a lot of bugginess comes into play.
It's funny that you say that because sometimes when people ask me, hey, can you look at my bubble application? And I'll go in, they'll give me access, I'll go in and the first thing I do is I look and see are they using backend workflows? Because for me, that is a clear indicator of whether or not you're a good bubble or not. Well, I don't want to say good because you could be really good at. But if you're not using backend workflows, you're not a professional.
What's so special about back end workflows?
Well, first of all, they execute on the server, so they don't depend on whether or not your customer has a, you know, M4Mac Pro Super Ultra processor with tons of memory. It doesn't matter if they're on a cell phone. It doesn't matter anything about, you know, what browser they're using or how old their computer because it happens on the server. So that makes instantly makes your application more responsive to the user's needs because you're not asking their infrastructure to do work that isn't necessary. So that's just good practice. Everything you can move to the server, do so. I mean, that's usually a good idea. Now if something needs to happen when a person clicks a button and it has to happen instantly, well then that's in a client side workflow and that's fine. And you can have them work together. So a client side workflow can offload part of its work to a backend workflow, and that's perfectly normal and a good way to do things.
