Bubble Appreciation

I’ve been working on a big new feature within our existing app. I’ve worked really intensely on it, non-stop for a couple of months, and finally launched it yesterday.

I can honestly say that this was one of the most enjoyably productive periods of my life so far, and pretty much every day while I was working I felt a sense of gratitude and massive respect for what the guys at bubble have created for us. Yes I encountered quirks and annoyances - but on the whole it was simply an incredibly positive experience, constantly leaving me with a feeling of “wow, I can’t believe I’m able to do this!”

At no point did I feel limited in anyway - anything I could want to implement I could, and if not with the native out-of-the-box tools then with custom plugins. For example I created an interactive midi keyboard for selecting musical chords - and whilst still possible with native bubble, it was easier with code. The beauty of this is how well it just “slotted in” to the current app…still feels totally native to bubble, with the right bits exposed to bubble and easily usable in workflows and conditions, and other parts abstracted away under the hood. I can now use this on any page with drag & drop. A real dream “best of both worlds” type of thing & brilliant dev-user experience.

Bubble is magic, somehow more than the sum of it’s parts. It’s frustrating to not be able to articulate clearly ‘why’ it’s so good and I do feel like bubble needs to also figure that messaging out and solidify it’s core brand identity/usp in light of all the new AI centric competition. For me it’s all about the very cohesive balance between front end/gui, the logic editing (workflows), database and the backend server workflows (the ease of time-scheduling workflows is a particular highlight). Everything is in reach and under my control - every workflow, every pixel, security, monitoring usage & costs, global issue tracker, API integrations, etc. Booting up one site and having my entire multi page web platform right there Infront of me is really something, and brings a smile to my face every time.

That’s it really, just wanted to share some bubble love & respect here… Cheers :+1:t2::heart::sun:

Areas i’d improve on first if I were dictator at bubble:

  1. database speed & SQL join logic. It’s “ok” as it is, but if it could be improved to be faster & more flexible & cheaper then that would really help keep users within the platform rather than reaching for 3rd party tools like supabase.

  2. interface. It’s getting better but still feel a bit windows95 and messy in places. Hire me for a week and I’ll polish/ redesign the entire thing for u :blush:

  3. index page loading speed & SEO visibility. Probably my biggest gripe/concern. It needs some kind of cloudflare static page layer pushed Infront to give people the instant load speeds they expect in 2026. This may feel like a nicety rather than a nesecerity but I strongly believe it’s essential. Clunky sluggish websites do not belong in this era.

  4. code export. The biggest criticism of bubble & turn off for many potential new users is the “lock-in” and not allowing people to “own the code”. I think you were once in a strong enough position to insist on this, but in today’s climate you may be causing yourself more harm than good. I get that you’ve promised self hosting if it goes sideways but Bubble should also now allow some kind of option to turn it’s user-friendly abstracted logic blocks (workflows) into clean “best-in class” code & allow it to be exported. I realise that some parts can not be easily exported but a compromise needs to be found. After all, it’s only a matter of time before an Ai tool comes along that will re-generate it all anyway, so you may as well take control of the process.

Overall bubble is awesome and should stick to (and improve on) it’s strengths: being a complete full stack solution with a great visual editor, solid backend, and intuitive workflow actions that abstracts away syntax & complexities, leaving us (both beginners AND advanced developers) to focus on the app design & flow itself. For lack of better discription I see Bubble as a central “mission control center” hub, simplifying the overview and management of complex apps - from prototype to production.

Final encouragement to the bubble team… You’ve built something very special. Keep positive and keep on course - if you double down on what makes you you, and own your identity, the rest will fall into place & the future brighter than ever :oncoming_fist:t2::folded_hands:t2::sun:

15 Likes

Keep it going!

Thank you so much for sharing. I shared internally with the entire team. It made our day.

3 Likes

Thank you

1 Like

Can only agree!

For me, this is the main issue.

I’m not a highly technical user — and that’s exactly why I chose Bubble in the first place. The whole value proposition has always been about building without having to dive deep into data engineering.

Today, however, I have a very simple app already in production, with a table that has surpassed 1 million records and will soon reach 2 million.

The problem is that, on the Bubble side, the only practical way to optimize this scenario is by creating multiple satellite tables, heavy normalization, and parallel data structures just to reduce query cost and search time.

This creates two major issues:

  • I don’t feel safe doing this kind of heavy refactor in a live production app.

  • Bubble’s costs scale very quickly, and right now there’s no simple, native, and safe way to optimize large queries without resorting to complex architectures.

What I really need are optimization solutions directly within Bubble — something that reduces database query cost and latency without requiring endless normalizations or advanced architectures that go against the low-code promise.

If the database layer were more efficient, faster, and cheaper — especially for high-volume data scenarios — it would go a long way toward keeping projects growing inside the platform, instead of pushing users toward external tools like Supabase.

@fede.bubble @emmanuel

4 Likes

thank you @gabriel15, I sent this to the team as well. It’s good feedback

1 Like

What issues are you specifically seeing with 1 million records?

For a well structured table, you shouldn’t notice any difference in search times compared to 1,000 records.

Is it cost of number of results returned that’s affecting you? Or the cost of inserting things into the database? Or something else entirely?