Monthly Community Update -- September 2025

Hi everyone,

This is the September community update. You can read last month’s update here.

The energy at Bubble HQ has been incredible lately. The team is working hard on bringing our AI vision to life and taking native mobile to the next level — it’s exciting to see the progress we’re making on both fronts. We’ll have official updates to share with you during our Bubble Tour events in October, and I can’t wait to show you what we’ve been building. If you’re near Paris or London, get your ticket! For everyone else, don’t worry — we’ll be sharing all the replays and recaps so you’ll hear the news too.

One big reminder that starting today, you can officially choose a native mobile pricing plan so that your deployed apps stay live once plans become required on October 1. You won’t be charged until October, but by opting in to a plan now, you can guarantee your app’s users won’t see a service disruption.

What we shipped last month

We made some significant behind-the-scenes improvements to database performance that should make a big difference for apps with especially large data sets or those that have experienced slow queries: specifically, around 50% faster database searches, up to 90% faster deletions, plus faster insertions and fewer query timeouts. We got there by adjusting the way Bubble apps’ databases are indexed, including fixing some inefficiencies and cleaning up and standardizing other aspects of the indexing process on our side.

For our Enterprise customers, we rolled out six new releases designed to help your business scale faster and more reliably on Bubble. These include 24/7 support, a higher uptime SLA plus an even higher availability configuration, database storage auto-scaling, our new trust center, and new dedicated regions. You can read all about these new capabilities here.

The agency directory is now the experts directory, and coaches (those who help teach clients how to build their own apps) are now included alongside agencies and freelancers (those who build apps for their clients). If you fall into that second category, you can also now ‌specify whether you’re an agency or a freelancer to help the right clients find you more easily. We also streamlined the RFP flow based on your feedback. Next up, we’re working to prioritize additional improvements like refining the payment flow people use to book coaches and incorporating ratings and reviews.

The toggle for the expression parentheses feature has been moved from “experimental features” to general settings. This feature allows you to write expressions with parentheses for clearer logic. It’s been working great for a while now, so we officially graduated it out of beta.

We shipped several improvements to Bubble AI. When you start a prompt from our website, we have some example prompts to help inspire you. Now, those appear in the prompt box that you see when you’re logged in, too. More elements are now fully supported in AI-generated apps, including multi-select dropdowns, searchable dropdowns, and radio buttons. And finally, you’ll now see logos that Bubble AI generates right in the editor, not just in preview (previously it showed an expression in the editor).

We also rolled out a couple ‌of Bubble Boosts. We improved the efficiency of “trigger a custom event when data changes,” which could manifest as WU savings for you, depending on how your app uses this workflow. Also, the expression composer now gives you visual confirmation that a literal value is accepted. In other words, say you had an expression like “email address isn’t: me@me.com.” That email address is a literal value. Now, when you type it in, you’ll be able to click on your text in the drop-down so you know it’s saved and valid.

As mentioned last month, we recently streamlined our bug report process. Thanks to your reports, the following bugs were fixed this month:

  • If you had a popup element open in the design tab, the app search tool would show behind it instead of in front of it. Now it properly appears in front.

  • If you signed up via a third-party connection like your Google or Facebook login, the AI prompt box would clear itself. Now it retains your prompt.

  • AI app generation sometimes failed after a high number of refinement prompts. We truncated previous prompt history to fix it.

  • When a custom event was triggered twice in a row, the event value was not always updating correctly the second time. Now it is.

  • Now that buttons can have an icon and a label, icons were not always following timing instructions for element transitions. For example, if you programmed a button to transition from one color to another after 3 seconds, the icon may not have followed the rest of the button. Now the icons follow instructions as intended.

  • The page manager didn’t always refresh in a timely manner when switching between branches. Now it does.

What we’re working on

  • AI

    • Most of the AI team is heads-down on bringing conversational editing capabilities into the editor. This is the next big step in our AI vision — being able to tell Bubble what you want to change and having it happen instantly while you maintain full control. We’re internally testing now and are still on track to bring its first iteration to you this year.

    • We’re also making good progress on getting ready to get the native mobile AI app generation feature in people’s hands for testing — internal testing is happening now.

  • Native mobile

    • In September, we’ll be releasing a feature to make it easy for end-users to reset their passwords directly in your mobile app. Magic login link support is also in progress, slated for October. These two features lay important groundwork for the broader deep-linking feature that the team has planned.

    • We’re also making more improvements to the native mobile deploy flow. Specifically, we’re giving you real-time confirmation that your App Store developer connection keys are valid. Before, you wouldn’t have known whether they were correct until your build was successfully packaged for the app stores (or not).

    • We’re aiming to test in-app purchases with a select group of users in mid-October, and we’re also still making progress on the mobile plugin editor, which is expected to hit beta in Q4.

  • Stability

    • We had an incident on August 21 that resulted in an outage of about 45 minutes when our internal load balancer had some connection issues with core servers. One of the main factors that led to those connection issues was an outdated piece of infrastructure — and so we’re removing it and replacing it with a simpler, modern alternative. That work will be complete by September 17.

    • Removing it will also eliminate the need for hostname and DNS changes when we balance loads across servers, which increases stability further. A byproduct of this change will be an update to the way we generate your app’s editor URL. Instead of appearing as bubble.io/page?id=[appname] or d100.bubble.io/page?id=[appname], it will appear as [appname].editor.bubble.io.

  • The property editor

    • With user interviews complete, we’re full steam ahead working on a complete redesign of the property editor. The changes will make it easier to use and more intuitive, especially for people learning Bubble for the first time. It will also be anchoring it in the sidebar, as you may be familiar with from products like Figma.

    • We’re working toward a closed alpha in October and a public beta in early November, during which everyone will be able to test it out, give us your feedback, and start integrating it into your daily workflow.

  • The table element is going out of beta. We’re excited to finally send the table element to GA with the addition of a few key highly requested improvements:

    • You’ll be able to add pagination and stipulate how many rows you want to display per page

    • You’ll be able to make footer rows sticky

    • You’ll get all the same workflow actions as you get with repeating groups (display list, go to page, etc)

    • You’ll be able to set alternating row colors

  • We’ll be updating fields in the ideaboard’s submission form in September. The new fields will give us deeper insights into trends and themes in your pain points so we can act on your feedback more quickly and strategically. You can expect to hear more from me in response to your ideas in future monthly updates.

  • We’re working on letting you view your WU usage by web vs mobile by October 1. This has been a common question since mobile launched — “how much of my usage is coming from mobile vs. web?”‌ ‌ — and we want to give you that visibility so you can make informed decisions about your app architecture and pricing plans.

Get involved

Applications for our next Bubble Ambassadors cohort will open soon! This is a huge opportunity to connect with the top 0.1% of our community and make your voices heard at Bubble. Bubble Ambassadors alpha and beta test early product releases, participate in feedback sessions with our PMs and engineers, get fast troubleshooting with the team via priority communications channels, and share community sentiment during new releases. If you’re ready to make an impact on the future of Bubble and no-code in 2025, keep your eyes on our social channels and email newsletters.

ICYMI

A huge congratulations to our Summer Mobile App Challenge winners:

  • Best iOS app: Scanimal, an app “designed to deliver vegan clarity beyond the label”

  • Best Android app: Tiny Emotions, an app that provides “an accessible and engaging way for children to learn about emotions”

  • Best companion to a web app: Zula Kids, which “makes storytime more inclusive, multilingual, and fun, wherever you are”

But truly, everyone who submitted deserves congratulations — one of the qualifications was successfully getting your app listed in either the App Store or Google Play, which is no small feat. We loved seeing the incredible apps you built!

Finally, the team recently filmed an awesome interview with Think Cater, a catering and events platform that handles everything from vendor management to event logistics. You can watch the whole thing here.

New hires

We had five new people join the team this month! Big welcome to:

  • Lindsay, associate product manager

  • Eliza, software engineer II

  • Josie, technical recruiter

  • Janice, senior software engineer

  • PJ, associate Bubble Developer

That’s all for this month!

‌ — Josh and Emmanuel

34 Likes

We love you! Keep it up and we’ll blow up the market together! :heart_eyes:

1 Like

i appreciate the timelines for native mobile features. thank you!

1 Like

This is a good day

1 Like

This might make it difficult to use on a laptop with a smaller screen. Will there be an option to disable it like we have now?

Excellent! We’ve had some great news recently in the evolution of Bubble. I’m very excited about the new features and improvements. Good job!

How to join “a selected group of users” to test it out this function?

1 Like

Charging for mobile apps before releasing in-app purchases seems backwards.

2 Likes

Thanks Josh, the performance improvement is visually noticeable, it makes skeleton loaders moot for a lot of my repeating groups since they’re now nearly instant. More of this!!

Could we also get these nested appropriately to show the logic at a glance without having to highlight the different parts of the expression and interpret Bubble’s highlighting logic? This is a trivial thing to implement because there’s a Chrome extension that already does the same thing.

Also, could you explain this more in depth?

2 Likes

Awesome update, looks like Bubble’s picking up the pace!

Great, thanks to the whole team behind this!!

Is this why when we add static values into the expression composer we now must press enter or return for it to be saved before we click outside of the dynamic expression to close it? I’ve been experiencing frustration trying to add numbers to operators like ‘+minutes’ or ‘is greater than’ and when adding in the static number, and doing my regular of closing the expression, the number is removed and I have to try again. In a coaching session last night, my student had same frustrations and I provided in the insight that now we must press enter or return for it to get ‘saved’ into the expression.

AWESOME! You guys should create a fun little game board at HQ that is like a Whack A Mole but for the Bugs, keep hitting them as they keep popping up, never let them stay up too long.

Nice.

Please make a very public announcement when this happens, as I’ll need to update direct links into the editor as some clients opt to just use the app data tab to get insights rather than implement an in app dashboard view.

Please put a quick link button in editor, and please add video record feature so that we can provide better clarity on how the idea would benefit.

2 Likes

Awesome update! Thanks for sharing

I’ve been critical of the focus bubble has had in the past, but things since seem to have been improving, for the most part.

The one area persistently (and notably absent) is announcements on bubble-built plugins, especially the API connector, which is insanely frustrating to work with, especially with the myriad of bugs in how it handles arrays vs. scalars (or lack thereof in the case of a null instead of an array). The maps plugin and multidrop down also get notable mentions. When will these be updated?

As a plugin builder, I would love to see some actual progress on documentation for the plugin builder (everything I’ve learned is from F12 dev tools and reverse engineering plugins!!!) and leveraging AI to help developers, similar to what Xano does.

Keep at it, but don’t forget that it’s the plugin community that keeps bubble relevant through adding features the platform to this day still doesn’t have…

3 Likes

thanks for the updates, welcome to new hires

Seems not ok to start charging for the Mobile App plan before you can monetize on your app. At least you should push your new pricing until you have IAP solved. We are not able to monetize the apps on the app stores.

1 Like

For me this is not a bug, but can you give an example?

A lot of API are poorly structured. The issue is not Bubble but API. However, because we are in a no-code world, we are limited on how we can handle API response in some case that could be easily be fixed with regular programming language.

The API connector is the only real “gateway” to translating a response to a bubble thing, so we define all our APIs and expected responses accordingly. If in your response you have an array specified anywhere (included in a nested object) - if you instead pass back a null for that value, you will get an error relating to “array_from”. This is simply the API connector’s internals (probably also something deeply integrated in the bubble internals) failing to recognise that the defined structure is not always going to have expected values, or indeed the correct type.

It means that every single one of my APIs I have a lambda in them to ensure an empty array is always returned, including within nested objects - as this also results in the same error if the nested object containing that array is a null value instead. This is not normal and should not be necessary, but for bubble - it is and always has been AFAIK. Other platforms that interface with these APIs have no issues whatsoever with null passed back instead of an array - and there is no standard that requires an empty array be used instead of null, nor does anywhere require a nested structure also be sent back where an array is included - all “hacks” I needed to add to my APIs to simply make them work with bubble (after spending months trying to troubleshoot these issues). Error example below:

image

In the DevTools:

image

To be clear - whilst this error is reported by my plugin, I am completely powerless to handle this as I do not have any way of knowing the expected return data for any API value - this is entirely handled by bubble’s internals as translated by the API connector, and is invoked only when publishing a state containing the full response.

In any case, trying to avoid polluting this thread with known bugs (this one has been around forever) - but nonetheless - the API connector and pretty much every bubble-developed plugins are very dated and need improvement and I think there really needs to be more focus on them.

Very much excited about this! Looking forward to see this in action.