[foxbee]

Thanks for the feedback. I really appreciate it. You don't have to go through that flow. You can just use the docs and run it using digital ocean, docker, linode, kubernetes...

But! We are updating our onboarding to be quicker. In re to app perf, it's a little surprising. It's an area we don't get much neg feedback on so I'm happy you reported it. I'll feed this back to the team.

[barnabee]

Thanks for the response. I'll definitely give it a proper look and try out self hosting. It's actually quite nice that you have a "Budibase DB" option which might come in really handy compared with OpenBlocks.

And yeah, I realise I could just self host immediately but I wanted to use the cloud version to decide whether to make that effort and that was where the flow sort of got in the way (though I wonder now if there might have been an option to cancel it earlier or skip it that I missed…).

Re: the perf, I honestly don't think it is all that bad, but interactions just felt a bit less instant straight after using OpenBlocks. It might even just have been the animations in the UI giving that feeling :)

EDIT: actually, a couple of examples of the performance difference I have just noticed are:

1. The speed the selection outlines of the components follow the mouse hover in the designer.

2. The speed of updates of the designer when properties are changed, for example OpenBlocks both updates the text of a text element in real time and does it nearly instantly, whereas Budibase waits for pressing enter (which I think is fine) and has a noticeable delay. The delays seems to be there with all property edits. It feels like perhaps a server round trip vs optimistically updating the display locally, but is definitely noticeable.