Which is faster? Doing it via backend workflow or client side using custom states?

Questions
1

I’ve been using custom states and running every work flow on the front end because it is much easier and beginner friendly, but now I am experimenting with running it on using backend workflow and calling the results via Return Data from API

I am wondering which is much faster and more efficient?

Thanks in advance!

2

Which is faster? Doing it via backend workflow or client side using custom states?

Doing what, exactly?

and have you tried it both ways to see which is faster for yourself?

and more efficient?

more efficient for what? (the server, or the client?)

1 Like
3

I second what @adamhholmes mentioned. Have you tested and compared the speed and user experience?

For me i always put user experience first. If your users are happy with your current front end workflows you should keep it that way.

Don’t forget that backend workflows will add a little more to your usage and may cause unexpected spikes if you are not careful.

2 Likes
4

Maybe consider reading this book by @petter… The Ultimate Guide to Bubble Performance - 156 pages of optimizing tips

2 Likes
5

Do you mean that front end workflows can handle more users?
Is it more efficient on server usage and that it will not affect the user experience?

My app is an article generator and I have a workflow that uses list karma to iterate on a list of article subheadings. Inside are 4 API calls and my users are experiencing cannot connect to remote server.

I was thinking that doing everything on backend will solve this issue

@adamhholmes