Form Autobinding vs Pagination (Workload Optimization)

Hi!

I have a long form with 30 fields. I know that saving these fields after using a “Submit” button will take a few seconds for Bubble to load.

Therefore, I have been looking 2 options and would love to know which would be the optimal for workload usage:

Option #1: Autobinding
As I see, each autobind will consume a bit of workload. Therefore, each form would need 30 autobinds.

Option #2: Pagination
I can group certain fields and add pagination to save data on each stage (group) of the form.

At the end, all 30 fields should be saved in the database. Which option would be better from a workload usage? Or should both options consume that same?

Thanks!

I wouldn’t suggest the autobinding route since you would need to create data first before you could use autobinding. If you factor in user drop offs, you would be left with a lot of useless data. Not to mention the WU it would consume since everytime a user unfocuses from an input, it would save the changes.

The best route you could choose from are either the pagination or the submit in one go. This would entirely depend on your use case and desired UX.

We have a form that has more than 30 fields which can also be dynamic i.e. up to 100+ fields and it doesn’t take that long to save the values from the input. There’s a couple of factors that would impact this though.

Hi @ntabs ,

Thanks for the help. I think pagination is the way.

Thanks!