So, as we are all considering bubble alternatives, I have a question about terminology.
I am definitely a no-code operator. I am looking at the options found through this thread and getting confused about what I can expect in front end vs backend.
i.e. a Setup like WeWeb and Xano
Comparing it to bubble, which one is handling which functionalities?
I get that front end is the design and UI, responsiveness etc.
And I get that the backend is the database…
But what about the “Actions” and “Workflows” from bubble? The part that says “When the form is submitted…”
Someone created a thread on the Wappler forum translating bubble terms into Wappler speak… which is the real word for things, so it would be applicable outside Wappler as well.
I would link to the thread, but when I did so earlier my post was removed.
A couple of things that come to mind is that going from Bubble to Wappler:
you need basic sql database knowledge
you need basic html/css/javascript knowledge
you need basic knowledge on hosting on a droplet and perhaps some docker knowledge as well
-handing authentication is much less turn key in Wappler
-batch processes are WAY faster in Wappler
-running ‘backend workflows’ is much easier/less confusing in Wappler
-adding custom code is much easier in Wappler
-if you are a novice developer you will experience (in my opinion, your miles may vary) quite a steep learning curve. This is partly fixed by this friendly community, but will be steep and fairly long, nonetheless.
-basic linux terminal commands
You can create logic (if this - than that) on the front end (WeWeb) AND/OR on the backend (Xano) - they both support logic. You can call also do API calls from WeWeb AND/OR Xano. So, I guess in Bubble speak - you can create workflows (WeWeb) or Backend workflows (Xano). As far as “actions” that would be WeWeb - but you can obviously “trigger” a back-end workflow from the front end. Also - worth noting that WeWeb already has an AI Co-Pilot in beta - AND they just teased this Figma integration as well - COMING SOON - Figma to WeWeb integration - YouTube
Yes, this is very true. Wappler defines itself as “low-code” as opposed to “no-code”. You will need very basic knowledge of things.
But depending how advanced applications you build on bubble, you also need basic Java and CSS knowledge. I use extensive CSS and a fair bit of Java when I build on Bubble, which is often problematic as it conflicts with Bubble code.
You also need a basic understanding of database structure, API, etc. to build on Bubble… they just call stuff differently.
@samnichols Please keep us updated on what you discover with flutterflow. I’m looking more closely at draftbit, but they both look interesting and powerful.
Ultimately, React Native and Flutter are the only two good options for cross-platform development, so I don’t see any other good no/low code alternatives for those who need mobile app functionality in addition to desktop browser.
Multi-platform is a must for us, too. Ideally I want something that makes it easy to get in the app stores and have a cross-device capable web app, which it looks like Fluttlerflow does.
@aj11@samnichols Wappler has its own reactive framework and also allows you to build web, mobile (Android & iOS), and desktop apps. I’m building mobile and desktop with the same codebase. Mobile and desktop apps are built using Capacitor, but it’s fairly straightforward “one-click” deploy from within Wappler.
How are they published? Is it publishing a wrapped mobile app or is it being published as in react native code?
If I’m going to put all this time into rebuilding everything I want our mobile apps to at least be react native or flutter as opposed to wrapped in a webview.
Thanks for the suggestion. It looks like way more of a learning curve than I’d be able to handle in 18 months while raising a family and also running a web agency in addition to my app, though. Looks like a great option for many, though. My background is conversion optimization, marketing, and strategy, not so much the coding side of things.
