I was going to say the same thing, need more data on these discussions.
ah interesting, Iāve never seen that before @boston85719 , looks like itās from before I joined the team.
Iāll check with the content team to see if they have any pieces like this slotted to come out
About a year ago I created this topic as a worried dev. I had not invested in my written communication so the topic is not well very well written. Many of you replied to that topic, so Iād focus on the replies.
If youāre a nerd you might want to read what people predicted and compare it to our current reality.
I have always detested the āecosystemā around Bubble. Itās like, Bubble is selling shovels to gold miners, and then a group of gold miners decided to sell guides on how to use the shovels, modified shovels, and extra hands to dig.
Hi Kelly, I believe Darwinian adaptation is required here.. Maybe teaching people how to best use Bubble with AI ā for example, Buildprint ā could be a direction worth looking into.
If the company fulfils its end of the deal and makes Bubble into the best product it can possibly be, iron out all of the issues, and add 2006 quality of life improvements, then Iām sure our community will be more than happy to continue to shout about it from the rooftops and be itās brightest ambassadors, and even new business ideas such as āturning chaotic vibe code projects into manageable Bubble projectsā could become a viable reality and career path.
Rather than leaving twitter/x because people are asking āwhy are you still using thatā itās an opportunity to stay and fight the case! I certainly try and often engage threads to help showoff what bubble can do and what people are missing or not seeing.
@emmanuel @josh Give us the best foundation possible and we will do everything possible to put you back top of the map! Bubbles community is one of its strengths and I for one am happy to help fight for this platform we all love. 
Yes.
And AI pretty much gave everyone a shovel. But there are a couple of big problems.
Iāve mentioned this on the forum before, as well as a couple of guest articles.
Thousands and thousands of apps are being builtā¦
but now the problem is nobody is using them.
The new problem (actually not new), but more pronounced to a whole new crowd, is how to monetize an app. How do I grow it? How do I even get users?
A whole huge potential.
AI has, in a way, made apps more human-reliant. Success becomes increasingly dependent on human instincts like understanding people, trust, timing, positioning, and what users actually care about.
A lot of things are changing, but itās important to really understand how to pivot with the changes
No-code existed for one reason: traditional coding was expensive and slow. Hiring a developer/agency costs tens or hundred thousands and takes months. Bubble has become the #1 no-code tool because it let people build real apps ā databases, logic, workflows, user accounts ā without touching code. I learned Bubble for the exact reason - to build apps faster by myself.
It takes new Bubble users (clients and developers) weeks to learn Bubble to build simple apps well. Most clients will need help when building Bubble apps that are somewhere complex. There are many best practices and optimization to learn and many workaround from trials and errors. That was why there was no lack of demand for mid/senior Bubble developers. Clients contacted me to coach them or helped them finish apps.
I understand the vibe coding has its problems and risks. But as we know, most MVP apps donāt succeed. Taking weeks to learn Bubble to build MVP was a workaround. And most of those apps have security and performance issues when scaled. However, with vibe coding, users can build MVP in a few days. The workaround is no longer needed. It is still much faster for users to build and iterate MVP with vibe coding. If it gets traction, it is pretty easy to hire a developer to clean up the app or rebuild it properly. But for Bubble apps, many clients need help to finish the apps before they go live. The initial funnel is crucial to grow into a big user base. This funnel for Bubble is disappearing or has gone.
I understand the Bubble has AI. But it is still so much behind compared to AI builders, e.g. Lovable, Base44, etc. Buildprint is great, but only experienced Bubble developers know about it as it is not integrated in Bubble. Coding is very flexible, too flexible as a matter of fact, that it is easy to create technical bugs with vibe coding. Building with Bubble reduces those technical bugs, as users can only build the app in Bubble ways. So most Bubble bugs are design/logical/implementation bugs. It should be very fast and more secure to build Bubble apps with AI. Unfortunately, as the OP has mentioned, Bubble has technical limitation/debt that has prevented it to be a real good option even when its AI programming feature become mature enough, e.g. the lack of if/else, return value from backend WF, backend variables, true loop, slow and expensive WF and DB access, and the need for workaround DB design to compensate Bubbleās limitation, e.g. sorting by option set and related fields. So whenever a client or a new developer asks me about learning Bubble now, I recommend them to check out Lovable first. Here is a recent quote from a founder client who learned Bubble to build her MVP app . She asked me to help her finish her app that was 60% done. She wanted to finish the app soon to launch in the summer, but she was lacking time and her budget was limited. After I understood her situation and her struggle, I recommended her to give Lovable a try first. 3 days later, she replied, āJust wanted to let you know I went on Lovable and was able to rebuild everything I did in Bubble in Lovable in one night. It was so much easier!! I finally feel like we can get this done much quicker. Thank you.ā I lost a client, but that was the right recommendation for her.
I do think there is a need for a full stack opinionated/structured AI first builder that can easily and consistently produce quality, secure, and performant apps and can easily support custom code. It could be Bubble but without its limitation. But I think the technical debit is too big to make it happen.
Iāve tested all the AI buildersā¦
spend a few hundred. I posted about it here before.
What are you going to tell your client if her Lovable app actually gets hundreds of real users?
Will you recommend she rebuild using code?
Just curious
The client was not able to finish her app. She was going to hire me to finish the Bubble app and it would have costed a decent amount. Lovable is code. Now she can finish the app herself. She can hire a dev to productize the app properly before going live if she chooses too, as she has the budget already for that. Many Bubble apps go live without proper security and optimization.
Ok.
This is kind of where we start to seperate nonsense from real sense.
Someone comes to me and says they want to build an app that explains what their cat is really saying when they meow.
Iām thinking, ok, this may be something a couple of your friends may use. Give an AI builder a try.
Then, someone has a great idea and I think it would be worthwhile.
A. Letās build the app from code
B. Youāre a startup with no funding yetā¦ letās use Bubble that is a no code platform and can do anything code can do and at a fraction of the price and when it becomes successful, you wonāt need to rebuild it. This is/was the original idea of Bubble
So, basically, I wouldnāt recommend any app I thought had potential to become anything being built using Lovable.
I guess itās really a difference in perception
I know a lot of people are mentioning Buildprint but the saving grace of that is that if Buildprint can enable AI in Bubble in a fantastic way thatās actually useful, then in theory, so can Bubble. It might take longer to get there, but it at least means itās āpossibleā.
The client was building on Bubble. She was not be able to finish the app by herself. She was short on necessary Bubble skills, budget and time. She didnāt have the budget to hire a proper dev to finish the app for her in a short time. The choice is either 1) no finished Bubble app or 2) a completed Lovable app. I think she has made her choice and was pretty happy about it. I did suggest her to hire me or another dev to productize the app before going live.
Got it.
And if the Lovable app works, then what?
Lovable app is a coded app. Lovable apps run in a full stack environment with AWS (like Bubble) and Supabase. It should not have scaling issue. When serious scaling is needed, the code is already GitHub. It can be exported and a more robust custom deployment setup can be arranged. The quality of any app (Lovable or Bubble) depends on the implementation.
When comparing a regular founder building with Bubble vs vibe coding with a fullstack app builder without 3rd party help, I donāt think Bubble has any particular big advantage that can easily persuade the founder to pick Bubble over AI app builders now.
Anyway, back to my point.
This is where good marketing comes into play.
You can actually help her before she ever built an app to determine if the app is actually going to be a success.
It shouldnāt be a thing of, well, Iāll build it and see if I get any traction.
This is where smart agencies can help.
You could have given the woman a definite answer before she ever built anything, and actually had users sign up. You could have, if you were a successful agency, already had a few hundred users signed up and ready to go.
This is 2026, where itās time to get serious about helping users
Honestly, discussions on some business things can be right depending on who is discussing them, and at what times it is in their career.
After tons of clients, business failures, and successes, a person looks at things differently.
Itās like the person who sets a goal to go from A to B, and thinks that if they could just get to B right away, their problems would be solved.
Actually, they wouldnāt, because itās the journey and everything you learn between A and B that helps you maintain your goal at B.
Also, a lot of times, by the time you get close to your B goal, your attitude has changed, and what you thought would be a great goal ends up not being what you really thought was worthwhile.
Anyway, have a great rest of the day.
Itās June, and the time of year for vacation, so I hope everyone does well with whatever youāre working on
Shouldnāt it be faster since they can use what you learned while building buildprint?
This event should be pinned to the forum, so more people are aware.
A lot of very thoughtful commentary and great advice in this thread. My perspective is that AI has both destroyed and created a ton of opportunity, both for Bubble overall and for everyone making a living on top of Bubble.
Reacting to a few comments:
Yes ā this is very much aligned with how weāre thinking about it. Weāre not going to stand out by how fast you can build and iterate on an MVP any more ā the best we can do there is break even. Where we can stand out is the long-term trajectory of apps built on us. Weāre trying to improve the AI experience (both our Bubble Agent as well as enabling tools like Buildprint) because we know that needs to be decent to get people in the door, but we think the reason for us to exist/thrive in this market is what happens afterwards, and youāll be hearing more and more from us on that. I 'm nervous about over-hyping the livestream weāre doing on the 3rd because I donāt want anyone to be disappointed, but Iāll say that itās the biggest drop of power-user-oriented features that weāve done for quite some time.
Agree ā Iām seeing this across all aspects of tech, both in no-code and code. The opportunities arenāt going away, but theyāre changing, and diversifying skill set, and unifying AI skills with traditional dev skills, are where they are at.
Our team has been doing some office hour sessions with a small subset of our new users, partially as an experiment to see how human intervention helps conversions, but also to give us visibility into those questions. Hereās an internal report we put together on some of the learnings.
Thatās the plan!
Yep ā lots of new opportunities, and a lot of them are shaped like āgo deeper into a builderās development journey and help them solve business problems, not just technical problemsā.