Sure im going to FlutterFlow, its better and i can learn Flutter with it. So i hit 2 fly with same tool. Bye
With Flutterflow, you’re limited to mobile apps, or slow web apps. And you have to learn Firebase, or any other backend anyway. Depends on what you want. But you learn JavaScript on WeWeb, which is more handy than Flutter imo.
@Broberto whats your experience looks like on flutterflow to conclude it has slow web apps ? im curious
1 Like
It’s not made for Web Apps and I don’t think it ever will. It’s doable, and it runs decently well. But for web apps, it’s not like flutter is for web, it is indeed for mobile.
Hi, I would be genuinely interested to know what you like more about FlutterFlow.
Because based on your list to be honest I think we are better, at least I don’t see any major difference 
-
You can perfectly recreate any figma in WeWeb, we’re still working on animation but our idea si to allow anything you can do with CSS to be done on WeWeb. And yes you can recreate Twitter or Instagram. Here a video of someone who did it => https://www.youtube.com/watch?v=IixchsBO0Pc
-
Yes to develop a web app you need to be a developer, our idea is to allow more people to learn how. Promising people they can create instagram without knowing anything about web development is a lie. You have to know the basics. In weweb you don’t need to code, but you need to understand how to connect your beautiful kanban with your database and we teach you how. We teach you transposable skill and concept you can reuse anywhere because they are at the core of the web.
-
Hey, you can see on YC combinator we are 2 years older than FlutterFlow. We was a static website builder before pivoting to web apps. We are still accelerating. We are not losing any velocity. we are increasing it.
The last 12 months we implemented our new multi branch Workflow system, classes, many integrations, new UI kits, new templates, code export and self host, backups, copilot, public API, staging environment, the Academy, and I can’t even remember every thing we released.
In the same time we updated our plans to better fit our users needs, by lowering the price of the lowest plan and adding more feature in the others, we had very positive feedback and we plan to continue listening to our users so our plans can continue to be relevant with the current state of the market and what they want to achieve with WeWeb. -
The whole point behind the split between frontend and backend is the scalability. With WeWeb as a modern frontend the scalability is theoretically unlimited. Yes, unlimited. Because you can export the app and host in on a CDN replicated everywhere in the world. Because we output a standard web application, with static html/js/css files. Because we stick with standard technologies (not dart, not flutter) we can easily be associated in any stack and it make us ready to benefit from any future evolution the web platform will receive.
-
As I said, one of the main benefit of decoupling is you can scale independently each part, because a backend and a front end doesn’t require the same things. The modern development has different optimised process to build and host each part of the app. And a backend can be used for multiple different front end. A backend cant be hosted on a CDN for example. Also, it allow more flexibility to update your stack. You can easily change the backend if it doesn’t fit your need anymore. You can connect multiple backend if you want. You can reuse your backend but change your frontend allowing you to keep your app alive while you’re developing the new front end and just switch when its ready.
-
Because they already have the infrastructure and resources for. Because they don’t want their app to be on the internet (enterprise network only). Because they want to scale it on a specialist like vercel, by deploying it themself on a CDN everywhere.
FlutterFlow has his own strength. They can output a mobile app for the Apple/Google store, and they invest a lot in marketing. I’m pretty sure our ever growing community would be happy to help you if you went back to give us a second try in some weeks. 
5 Likes
Thx this response but Weweb is pricey and only Web apps and fronted while FlutterFlow mobile/ Web app and much cheaper and has no visitor limitations. And here I need to pay for the backend too if I know correctly. I’m not self-confident to start a web app without a holding hand. The community is really small, I barely heard of this application, I found it somewhere in a post on Reddit only once and nobody knows what is this. YouTube videos or comparisons are nonexistent. So I’m not confident to use this. I’m not a web app developer I just have some startup ideas as a game developer…
FlutterFlow has better UI and community, and i can make mobile apps too and, if it has better marketing I don’t care. End of the day I want to make a startup with a good tool, if the tool is not enough or I’m not confident to use it, I won’t.
And marketing means they have money, money= users = more money = more users, Basically its a cycle where the company gets loads of users and money so they can operate better and be more stable… don’t use marketing as an excuse. If this software is older by 2 years why is the team not marketed as heavily as they?
Change my mind.
I can be wrong but I’m pretty sure you also have to pay for an external backend for FlutterFlow too.
I understand the app visit can be frustrating, but I’m confident saying a project with 250K visit a month can afford an higher plan with unlimited visit. Be aware a visit is a session, someone changing page on the app will not be counted as a second visit.
I didn’t want to be judgmental. Investing in marketing is not bad. I mentioned it because of course it has an impact on the public exposure and the brand recognition, as you seemed to worry.
The current product is not older by 2 years, only the company is. It was to say even if the product is young, the company itself has proven it can adapt to the market, innovate, and continue to deliver over time.
We are stable enough to not have to rush things, we are still consolidating our fundamentals and preparing the field for game changing features like editor versioning, reusable components, marketplace, Dynamic SEO, and much more.
Both product are free for building so you can try them both and choose the one you’re more confortable with. It depend of your background and what you want to build as product for your startup ! The right tools for the job.
We like to recommend Webflow when you want to build a beautiful landing page with the best possible SEO for example. And we can also recommend FlutterFlow if you want to build a native mobile application. But for a web based business application, a SaaS, a marketplace, anything a little complex with a lot of interactions that people visit through their browser, mobile like desktop, I would said WeWeb is a really solid solution.
I’m not trying to change your mind. I’m just taking your post as an opportunity to share our thoughts, strengths, philosophy and ideas with our community. And because as a web developer, I’m passionate by what we are trying to achieve and I like to discuss the different approach everyone are taking.
4 Likes
Flutterflow is Firebase, so yeah. Not even suited for all the Apps, while Supabase/Xano is a relational DB (pgsql) so you can build almost anything with it…
My two cents here… I came from Flutterflow and Bubble, each with their unique cons/pros. If the intent is to have native apps for IOS and android then Flutterflow is the way to go but they are a little lacking on publishing as a website. Bubble does web development fine but if your application relies on large datasets then it’s internal database will be the limiting factor. Unless you have experience with Flutter, the learning curve for Flutterflow is a little steeper than Bubble but all of these platforms are easy to pickup within couple of days. I have settled with WeWeb as for my purpose, it’s integration with Supabase and Xano is great. The more I use WeWeb, the more I like it.
4 Likes