Would changing the auto-save functionality in the app builder - to a “Save Now” button drastically decrease the load on the servers???
If (let’s say) 100,000 no-coders are working away on apps and it’s auto-saving every action or so many seconds… isn’t that a tremendous decrease in apps / server / performance??
I would gladly click save and most likely not until after a few items were “completely changed or edited” - take that…MULTIPLIED TIMES 100,000 - would equal a LOT of performance enhancement!!!
Is this correct David??? I’m sure it’s a difficult balance to decide on from an “Adalo / Business” perspective, but wouldn’t that be a significant trade of performance for the auto-convenience trend in the past few years? Myself, I like a good, controllable button if this is correct…