Monthly Community Update -- November 2023

Hi all,

This is our November community update! Read last month’s update here.

Of course, the most exciting part of October was BubbleCon, our first-ever user conference. I had an absolutely amazing time, especially putting faces to names for so many members of the Bubble community (and learning new names!). I was blown away by how many people flew in from all over the world or joined us online, and the friendly, community ethos was incredible. I’m genuinely thrilled about what lies ahead, and we can’t wait to continue to shape the future of technology together.

If you missed it or just want to relive the magic, you can watch a replay of every single session. That includes the keynote that Emmanuel and I presented, where we shared some very exciting things to come. Speaking of which …

Highlights from the BubbleCon 2023 keynote

I hope you’ll take the time to watch the full replay or read an in-depth recap of our keynote here. But for now, here’s a quick list of the roadmap updates we announced:

  1. Native mobile: You read that right. We’re setting out to make Bubble the default no-code platform for not just web apps, but native mobile apps too. Stay tuned for updates by joining the waitlist.
  2. AI-powered design: AI and no-code are a match made in heaven, because both exist to make software easier to create. We’re bringing AI into the Bubble editor so you can kickstart full-fledged apps from scratch just by describing what you want.
  3. Bulk data operations: We’re committed to making data processing at scale faster and more efficient. New bulk operations will let you run backend workflows on millions of things reliably and cost-effectively.
  4. A revamped expression composer: Many of you have previewed this feature because it’s ‌currently in beta. The goal is to make building on Bubble even more flexible and easy to use with simpler editing, automatic parentheses, and better keyboard controls.
  5. Returning data from custom events: Soon, you’ll be able to add one or more fields to each custom event indicating the names and types of data it can return. The result is cleaner workflow tabs that make apps easier to maintain and organize.

For more, you can also check out the replay of VP of Product Allen Yang’s fireside chat on our product roadmap here.

Changes we made this month

Speaking of bulk data manipulation, we rolled out a change that increased the scalability of “Schedule API workflow on a list” by ~10x! We also shipped an improvement that makes it much faster to switch between the editor’s tabs — especially if you have a complex app.

In response to your feedback, we’ve simplified our bug report form. We’re exploring further ways to improve it, too, since we know overhead in submitting bugs is a pain point.

Enterprise customers on dedicated instances now have the option to disable Bubble employee login into their dedicated box. This was a request we heard from some of our largest customers, and strengthening our data privacy and security is an ongoing effort.

The Bubble Developer Certification is now available to everyone; no more waitlist! Register to take the exam here if you haven’t yet.

Finally, our marketing team launched a new homepage design on bubble.io as part of a larger, ongoing effort to refresh our website — we hope you like it!

What we’re working on

As Allen outlined in his fireside chat at BubbleCon, our product roadmap’s big bets are made possible by our core technology, which is why we’re reinforcing our foundation in Q4 and beyond. Currently, we’re working on:

  • Rolling out an improved test framework that makes it much easier for us to create and debug automated tests
  • Continuing to build automated tests that make sure our most important features have good coverage
  • Memory leak–detection and analysis tools in the editor
  • Breaking services off our monolith to make them independently deployable and observable
  • Error boundaries in the editor, which help ensure that if there’s a bug, it’s contained to a single component with clear feedback — making the editor less glitchy

The team is also elbow-deep in work on the new expression composer beta, continuing to fix bugs and refine the experience based on your feedback. In particular, we heard you when you told us you strongly prefer parentheses over brackets, so we’re finalizing a new design treatment that should roll out soon. We’re excited to see more and more people toggling this on and trying it out.

The AI team is improving our model’s ability to generate responsive page designs, and we’ll start usability testing soon. And the native mobile team has broken ground on foundational engineering work (reminder to sign up for the waitlist to get updates and early access!)

The team is making progress on improving “delete a list of things,” and we hope you’ll see a noticeable difference in scalability very soon, plus with enhancements to the log it generates. This team is also working on performance improvements to uploading CSVs of data.

Our onboarding team is running a new experiment where new users can tell us a few key features they want to build into their apps, and then we generate a custom starter template for them based on those features.

And some other projects that are still ongoing without any major updates just yet:

  • As we phase out all the ways apps were impacted by capacity limits, we’re making a change to keep you from incurring workload for partially executed actions
  • The team is building out the ability to create, edit, and delete a custom set of design breakpoints in an app
  • The styles tab is getting a new look and feel, improved search of element styles, a new ability to edit styles from styles list, and better organization and grouping of element types
  • The team is switching Bubble over to a more modern JavaScript bundler, which will lead to across-the-board improvements to page load speed
  • We’re refining our AI-powered RFP spam detector, designed to cut down on noise so that agencies and prospective clients can find one another more easily

Finally, we know some of you love watching the countdown of the remaining CoffeeScript in our main codebase! (#ASMR) Well, we just hit zero! We’ll be drinking lattes to celebrate.

Other updates

Plugin creators, friendly reminder that you have until the end of year to update any plugins with server-side actions to Plugin API v4. This update is simple (it just involves you swapping some syntax; check out the update guide), but if you don’t update them in time, your plugins will break — and any Bubble apps using those plugins will break, too. End-users will start seeing notifications in late November about any plugins that haven’t been updated, and unupdated plugins will be delisted from the marketplace until they’re fixed.

Also, major congratulations to our Immerse Demo Day winners:

And to our 2023 BubbleCon “Bubble For Good” Hackathon winners!

  • Bubble Rookies winner: Aanya S. (who is only 14 years old!), whose app empowers people to contribute donations to charities fulfilled by local street vendors
  • Bubble Veterans winner: Daniel N., whose app is an AI-powered sous chef that suggests healthy recipes based on people’s preferences
  • Professional Bubble Developers winner: Daryl J., whose app conducts mental health check-ins for kids and teens

Team news

We had three new team members join in October: Ally joining us as a senior software engineer; Kelsey joining us as a finance and business operations lead; and Becky joining us as a senior product marketing manager.

And if you missed them, be sure to check out Bubble Developer Andrew Vernon’s personal story and top Bubble advice on the blog, as well as why Director of Founder Inclusion Nichole Bestman believes the future of no-code is bright.

__

As you can see, it was a big month for the Bubble team, and we couldn’t be more excited about what the future holds. Thank you for reading, don’t forget to check out the BubbleCon replays, and we’ll see you back here next month!

Wishing you a fantastic November,

Josh and Emmanuel

40 Likes

Great! But only enterprises? Really? Only people that pay $3800/mo get peace of mind that only they have access to their data :man_shrugging:

cc @code-escapee on your recent topic

3 Likes

would be really difficult to do for a shared cluster?

2 Likes

Indeed! Thank you!

:+1:

(Sometimes the little things make a big difference when you spend all day in the editor.)

12 Likes

Does it not refer to employees not being able log into the editor area? Maybe I’m mistaken. - currently on shared any support employee can go check out an app, and even though I don’t doubt the integrity of the employees, it spooks clients a little :confused: I thought this update allows dedicated to disable that. Or do you mean that even if support had access limited on shared the engineers would technically still be able to access it?

1 Like

Does this mean that we can leave the “time between workflows” field empty and it will be optimized more effectively now?

1 Like

If it’s an issue it’s an issue for all.

Shouldn’t it be simple to ship this for everyone once it’s available for anyone?

2 Likes

Devastated that we won’t get anymore coffeescript updates. End of an era. Looking forward to the bulk data operations improvement so I can backup / export things from the db.

8 Likes

@josh a question on this one if I may:

In terms of custom events inside of reusable elements, I understand that this means I can trigger an event from the parent page and get returned values to that parent page.

However, what we really need to make reusables perfect is to be able to define public events inside reusables that can be picked up the parent page. This will let us trigger workflows inside a reusable and then have a subsequent event fire on the parent page (as in a public event was triggered). That event can of course ferry values from the reusable to the parent.

This post on the ideaboard sums it up.

You can imagine a combo-box component that tells the parent page whenever a new value was selected and passes that value in the public event.

Is this on the radar at all?

please say yes please say yes…

10 Likes

I think for support they have to adhere to SOC2 right? Only second tier support should be able to see your data. But maybe @josh can clearify this!

1 Like

Brilliant! Can’t wait to tell bubble AI that I need a responsive sub-page and then submit it to the AppStores.

Having an AI system that builds responsive pages/apps sounds incredible!

1 Like

Interesting update on the:

Speaking of bulk data manipulation, we rolled out a change that increased the scalability of “Schedule API workflow on a list” by ~10x! We also shipped an improvement that makes it much faster to switch between the editor’s tabs — especially if you have a complex app.

I rarely use this because of how inconsistent it can be. Really glad to see improvements like these.

MOST excited for the mobile app!

1 Like

A lot of exciting updates in this post…but wow I just tried out my editor and the change is amazing, way to go Bubble team!

3 Likes

Returning data from custom events at last! Super stoked for this as well as bulk data operations and mobile app support. AI-powered responsive design sounds interesting too, I can’t wait to take that for a spin.

2 Likes

Expanding this more broadly is on our radar! For infra reasons, it was easier to do on dedicated than on shared, so we decided to roll it out for dedicated rather than sitting on it til we could get it working on shared as well.

Not quite yet – that’s going to be covered by the bulk operations work we’re doing. This change was about how big a list can be scheduled without the initial scheduler action timing out.

No promises on that specific feature but we’re looking at various ideas in the modularity / reuse space

11 Likes

Is there a preview of the hackathon winners’ apps? Curious to see the winning apps!

on the reuseable fields I’ve noticed a persistent bug with checkbox/boolean

it constantly reverts to the default value even after changing it - but it only looks to be reverted in the editor, the actual logic for if it’s been checked or unchecked stays the same and works as intended on the app - kind of.

it seems to be inconsistent but I can’t tell if it’s the app or me because the checkbox displays as the default value rather than the value I set it to

to get around it I’ve used an option set yes/no and that resolves the bug since the option set value holds and displays fine

Solid update! Good work guys.

I feel pretty much everything we need to do on bubble can be done. Now it’s mostly quality of life stuff.

Looking forward to ai, native and bulk operations

@josh about the return data from custom event, will the same logic be applied to backend API workflow ?

Actually, the only way to get data back from backend wf is to trigger them with an API call (and return data from API action in the bwf) so any change needs to re-initialize, some pain to get it work and maintain (not pointing anyone from my team who has broken my call lately :rofl:).

Very nice news btw but already told you :love_you_gesture:

Was very cool to meet you in person + other member of the team like @theo.goldberg @carly @grace.hong @michael.lee @jayvee.nava @Calypso_BubbleSupport… and indeed @Andrew.Vernon , @sam.morgan and my deary @madambrose I already know from the #Bubblehouse :smiling_face_with_three_hearts:

5 Likes

Will the mobile native be offline capable?

4 Likes