the major issue here is you still wont have the ability to export code with either of these. Also depending on your app you may need weblow and wized and xano (or a alt) . Feels like a bad dream.
Iām using replit and it is great. Just like with bubble, you can deploy your code with a simple click on the āRunā button. With help of ChatGPT I already created a lot of endpoints Iām using internally, hopefully will release them to production soon as B2C services.
It has a copilot built in feature, which is not perfect, but as I said in a previous comment, complement it with ChatGPT and you are ready to go.
Itās kinda funny to see all comments saying āall-in Flutterflowā, āall-in ā¦ā.
Iām on it since 18+ months and as much as I love the tool for mobile use, if you really do think youāll can copy paste your Bubble app within FF, youāre a bit optimistic.
As Flutter is amazing for multi-plaftorm (iOS, Android, even desktop app), the web xp / feeling isnāt that great.
Scrolling is weird, rendering is also sometimes weird and it doesnāt look quite like a traditional SaaS webby experience. It rather looks like a tablet/mobile app embedded on a web page.
Flutter team made a promise to improve the framework on web (also with WebAssembly) but itās not quite ready yet, and JS, vueJS are still way ahead on web.
Not mentioning the thousands of plugins existing on Bubble that youāll need to either code or forget about.
Also, as Bubble can be 100% used without a single line of code, if you donāt know a bunch of code (Dart), do not imagine that youāll be able to do everything you made in Bubble there.
Iām not trying to advocate for Bubble, but all the alternatives have their positive / negative sides and you should be objective in your decision to change.
I see a lot of people entering into the āaha discovery momentā telling everyone to leave for a better world while they did not still encountered the dip that would make them understand that it might not be a better world (for their specific project).
Hope this helps!
Can someone explain me a bit more How it works to lock-in the price for the comming 19 months? I am in the personal plan.
The monthly price will increase by 10%.
You are then on that plan for 18 months, unless you move to the new WU plans.
After 18 months you will automatically be moved to a WU plan.
Thanks Nigel! So i can just proceed for the next comming 18 months with my personal plan?
As it stands today, yes that is right.
Been doing a ton of digging and exploring options. Our planned new stack at the moment is this:
DraftBit for React Native iOS and Android apps.
Weweb for a performant web browser app.
Supabase for backend.
No vendor lock-in. High performance on all platforms. Unlimited ability to extend with code as needed. And complete ownership of the code.
Overall cost for all three will be roughly the same as weāre paying for Bubble now. Maybe a bit less.
Weāre going with DraftBit over FlutterFlow because weāre more comfortable with JavaScript and prefer our native apps being in React Native rather than Flutter.
Good point about Draftbit & Javascript.
Using Noodl.net for front-end (web & mobile) and https://www.back4app.com (Parse) for backend for now.
But like I said before, hopefully Bubble will pivot and come back with a reasonable pricing model.
Hi @aj11 , Iām playing with Xano and found out that it does not provide real time data. I should be polling every second from Bubble but it looks like quite odd. Can you tell if Supabase provides real time data?
A possible alternative could be to create a workaround using a Xano plugin for real time chat (Ably) but I donāt like very much the idea.
The pricing is based on concurrent connections and number of messages sent
Doesnāt Noodl have its own backend?
Yup, big hole in Xanoās offering. You can fix it using Ably, but looking at the guides it seems like a hacky solution.
Iām almost certain weāll be going with Supabase for two reasons, as @dorilama has recommended.
A. Real-time data functionality.
B. The least amount of vendor lock-in (they actual brag about having less vendor lock-in than AWS and Firebase due to being 100% open-source.
Despite all the above, and not actually branding themselves as no-code/low-code, managing most of the tool is visual. They compete directly with firebase, but even compared to firebase they have more visual interfaces to build with vs having to work directly in SQL.
All in all, it appears to be the backend option with the least amount of vendor lock-in, least amount of limitation, while still being mostly no-code.
Yeah, they do indeed but it is a limited runtime environment. We need specific npm packages which are not available (yet). They are building some kind of plugin feature btw, this will allow devs to use other NPM packages.
Hey everyone, Iām still having a rough time finding something that I prefer over bubble. Iāve tried FF but Iāve become really confused with how to get the responsiveness to work similar to bubble. There doesnāt seem to be options to set a max and min width and I canāt get elements to stack when the page decreases in size. Also the testing of the app is just not user friendly enough for me.
Iām trying to create a price comparison site and itās not too complex but I canāt find anything which competes with Bubbleās logic. Anyone have any suggestions?
Thereās a community in Brazil of developers, designers etc that will try to put together our own nocode platform, we saw some open-source projects that has potential but can be improved, the idea itās to fork a project and work from there.
Thereās some premises we will follow:
- Open-source project
- Export code function
- Self-hosting capability
Anyone who might have interest in the project and can contribute somehow, feel free to DM me.
We have a call later today where we will gather the staff and define some other things, Iāll keep you guys updated.
Annnd⦠If everything fails, noodl+xano looks very promising!
Definitely Bubble is not an option anymoreā¦
You have put put things in a ācontainerā and then you can sent the max height and width. Thinking FF is the best option for my case.
You should be careful to state someone is confused and then leave the discussion with out any arguments. I am not confused. Svelte/sveltekit is very different and simpler for rendering/routing with ie. React. I did not say that can jump right on svelte without learning Javascript, but it is fully possible to pick up as you go a long. Just as you have to pick up stuff in Bubble a long the way.
Hey, if you want I can explain why it looks like you are confused: react does not wrap elements with anything. It renders html elements to the page. You may find frameworks that wrap links to handle SPA routing, but not all of them. React and svelte do exactly the same thing, but have different systems to handle DOM changes and reactivity.
If you tell react to render an anchor element it will render an anchor element without wrappers.
this
{#if porridge.temperature > 100}
<p>too hot!</p>
{:else if 80 > porridge.temperature}
<p>too cold!</p>
{:else}
<p>just right!</p>
{/if}
is not a bare minimum requirement in the same way this
<li className="item">
{isPacked ? name + ' ā' : name}
</li>
is not a bare minimum requirement.
They can be both confusing without a solid base.
you donāt write HTML win neither of them, you write JSX with react and a superset of HTML in svelte. Both of them will be transformed and very much different from HTML.
Of course you can write js in react.
Of course you can write css in react, both in the component file and in an external css file.
Again, I do like both, so for me there isnāt a good one or a bad one.
If you felt offended I apologize. You seem a bit aggressive though so I am not going to reply anymore on this matter.
Peace