tl;dr The initial hurdles are much bigger than the ones after if you can hang in there at first (these concepts only have to be learned once!)
Hi Ash, I think a lot of the reason Bubble seemed so simple is that a lot of options were set up in the background (server type, connection, etc. – and whatever choice was made is the only option you got, so it’s easy to use Bubble without knowing how to choose these options)
But after just using the Wappler app a few times, the difference between editing locally and editing remotely in a browser is huge! Saves are fast, edits don’t feel clunky, and even the trackpad interactions are better. So I am seeing some positives right away.
But, like many development programs, Wappler gives you a lot of flexibility. If I am understanding right, with Wappler your project looks different than on Bubble.
On Bubble your web browser was used to do this: Idea on Bubble > Add Functionality > Add Data > Test > Publish
On Wappler, these same steps can generally take place and in the same order, but you will have the Wappler app on your desktop for development, then you can test locally OR online, then you publish to a web host of your choice. Bubble handled these steps in the browser, but on Wappler some of these steps will be in the desktop app, and others will be with your web host.
So, although the lingo and steps may be foreign seeming, there is a lot of overlap in the general frameworks if you have much time in with Bubble. In fact, I see a lot of the same basic underlying libraries as options in Wappler that Bubble uses (oddly, Bubble’s version is way older if I am reading right compared to Wappler’s included versions)
Getting acclimated is definitely going to take some time and effort, but I think that Wappler might be the best fit out there as a Bubble replacement (without losing flexibility; there are some options like Bubble that have some features of Bubble but aren’t flexible enough)
Best of luck and please keep us updated on your progress if you continue.
