Forum Academy Marketplace Showcase Pricing Features

Monthly Community Update -- October 2020

Hi all,

This is our latest monthly community update. You can read the prior update here: Monthly Community Update - September 2020

This month, the team put a tremendous amount of energy into hiring. Across the various roles we are looking for, we collectively did 144 interviews. This is a necessary investment for the future, but it also takes up an enormous amount of time and energy from the team, and led to a pretty disappointing month in terms of progress on our key initiatives. That said, I feel good about making this investment because it’s obvious that we’re going to need a significantly larger team to stay on top of the growth of our users we’re seeing and to continue to improve the platform.

Changes we made this month

On the community, training, and education side of things:

  • We’ve made significant improvements to our bootcamp program including building a new student portal and working on standardizing the curriculum. We’re also hiring more instructors – drop us a note at [email protected] if you’d like to apply!

  • We opened applications to our pre-accelerator Immerse for Black and Afro-Latinx founders and have started interviewing applicants.

  • We launched our second Bubble courses video series: Bubble 102 - Fundamentals.

  • We’ve started hosting live workshops in partnership with Makerpad – we’ll be posting the videos of them to the forum once they’re available!

  • We launched a new Help Center with articles answering frequently asked questions that we get.

  • We’ve written two new in-depth blog articles, one on the history of visual programming and a complete guide for getting started building web apps.

  • In addition, we’ve continued our App of the Day series with 20 new interviews!

On the product end, we didn’t make any major changes, but did release a couple minor things:

  • We released a new breaking change (version 9) to fix some weird behavior with referencing the result of a previous step.

  • We built the capability for our team to send emails to all users of a particular plugin, which is useful in case there’s an important bug or security fix.

Finally, we invested a lot of time into behind-the-scenes initiatives that will help us move faster going forward:

  • We finished a big chunk of the work we were doing on our internal analytics system, to help us get more visibility into what’s working and not working in terms of our features and initiatives, as well as how the various apps on our platform are thriving.

  • We reorganized the engineering team into sub-teams to make it easier to stay organized and train new hires

  • We brought on an engineering intern, Henry, who will be working with us through the spring, as well as extended a number of offers to interns and full-time employees who will be joining us later this year.

This month in numbers

(Note: we switched from Helpscout to Front this month, so changing the format slightly)

  • Total customers who reached out to us through bug reports or [email protected]: 2,540 (up from 2,014 last month)

  • Total received messages: 6,805 (up from 3,293 last month)

  • Average response time to messages: (3h 00m during business hours)

  • Time to resolve bug reports escalated to the engineering team: for bugs resolved in the last 4 weeks, it took on average 4 days for engineers to investigate and deploy a fix or find a workaround for the customer.

Things on our minds

We still have a lot of bugginess in some key features, which is disappointing and something we hope to fully wrap up by the end of the year. The big culprit is still version control, which we’re still working on, but we’ve also been investing more time into fixing bugs with our rich text editing plugin, since we’ve noticed that it’s been generating a constant stream of issues. We invested in better testing procedures for the rich text editor, which will hopefully lead to fewer bugs down the line.

Other than that, the main thing on our mind is building the team, via hiring, training our existing team, and building the management structures we need to scale. That kind of investment is really costly, but it’s necessary to move the needle longer term.

What we’re currently working on

New initiatives since the last update:

  • We’ve kicked off a project to simplify our codebase via reorganizing the graph of what files depend on other files. This is another angle we’re working to make Bubble more reliable, since a simpler codebase leads to fewer bugs, and to make it easier to get new engineers up to speed quickly.

  • We’ve broken ground on the project to build out a better responsive editing engine. At this point, we’re building a proof-of-concept engine to let us experiment with different editing paradigms. Our working hypotheses is that we’re going to do all the runmode rendering via flexbox css, which provides a flexible and high performing framework for building out layouts. The way we expose that to users via the editor is what we’re prototyping and playing with.

  • We’re working on updating the different user surveys we have (in onboarding, when creating a new app, …) to get a better sense of who our users are, so that we can design better experiences for different audiences.

  • We’re merging the Bubble reference into the manual to create a unified experience for our written documentation.

  • We’re planning on starting up webinars again. Quick poll for the community: would you be more interested in:

  • Introductory content to help new users
  • Deep dives into advanced technical subjects

0 voters

Updates on our ongoing initiatives:

  • We’ve started sponsoring more hackathons, and working on figuring out what a scalable package is for doing this going forward.

  • We’re working on the next Bubble crash course (“Building your first app”) and are launching two new series: “What’s new” and “Quick tips”.

  • No progress on moving apps between different databases, and moving more of our asset-building onto our new system: in both cases, we don’t have enough engineers to assign to them right now, though we’ll be starting back up at least one of them and hopefully both of them this month.

  • We’re expecting a rollout of splitting the main cluster into two release tiers, Immediate and Scheduled, sometime this month.

  • We’ve gotten the majority of the way through our Zapier integration, and hope to roll it out this month.

  • The complete redesign of our editor continues to make progress: we’re wrapping up the Styles and Data tab, and are through most of the Plugin tab. This month, we hope to transition from doing the initial buildout into the testing and integration phase. There’s still a long way to go til we rollout, but moving from building it out initially, to getting it all tested and working is a major milestone that we’re excited by.

  • Hiring: we are now looking for designers, engineers, and members of the Success team! For the Success team in particular, we’d love to hire someone who’s an experienced Bubble user and would like to help out other Bubble users.

Thanks again to everyone – we really appreciate the community and the support we get.

All the best,

Josh and Emmanuel


Sounds great guys!

1 Like

great work!


Thanks for the update.
Reading this thread I can clearly see Bubble is growing a lot, but I feel Bubble is avoiding some key “features” that 90% of other no-code tools have @josh and @emmanuel

What’s the real bubble “target platform”? Why still we can’t deploy real native apps for mobiles? There’re any plans in near-future for mobile development? Is mobile something not doable actually because on how Bubble is made? Since Bubble was founded (at all this time) don’t you think there should be at least an official way to get a decent app (and not a wrapper)?

Will Bubble always be accessible from a browser? Or there’re any plans in the future to have a dedicated app for each OS?

What’s the Bubble team criteria to select which is the next feature to add?




Something else to consider… I really really like the contextual links to relevant documentation from the bubble editor. Unfortunately, it doesn’t seem that’s continuing to be updated. Can you confirm whether that functionality is part of the new interface redesign? I sure hope so. It would be ultra sweet if a contextual link could bring up the official documentation as well as forum search results in a single unified interface.



Thank you for the update. Give us a tease of that flexbox editor ASAP :smile:


Short version: yes, it’s possible, yes, we’ll do it some day. Not soon though – it’s hard. We’re considering working on building clean support for Progressive Web Apps as an easier way of moving in this direction.


Native Apps, that would be a game changer and a-maz-ing! I didn’t think it was possible, I thought maybe a wrapper was the only option. Wow :hushed:


For All Your No-Code Education Needs:

  • One-on-One Tutoring
  • eLearning Hub
  • Video Tutorials
  • No-Code Classes

This, so much this ! We’ve been in the chat with @arthur.kieffer and how the custom actual responsive engine is so not standard making traditional front end devs not wanting to enter this game. Flexbox is the way to go !! Congrats.

On the other hand, it makes me wonder how much should I invest in time to understand and dominate a now officially deprecated responsive system . Any ETA @josh ? Like a year ?
Good weekend everyone

edit :


@Glideapp pwa support is a good inspiration to follow


It’s good to see the transparency, I understand the people implementing all the course and learning are probably different than the ones doing the building but I would have liked to see more progress on the platform than things like boot camps and education.

Nonetheless it’s challenging times and I don’t for a second claim to have any understanding of what it takes to call the shots you need to call.

Well done, looking forward to next month


Since we’re still proof-of-concepting, no timeline yet. I’m hoping it’ll be on the order of 3 - 4 months, but my track record for these kind of estimates is not particularly good, so I would take that with a massive grain of salt


Hi @josh. A related question: How will the eventual roll-out of the new editor impact existing apps built on the legacy editor? Apologies if you’ve already answered this question elsewhere.

1 Like

This is also TBD: once we’ve finished fleshing out the prototype of how the new responsive editor will work, we’ll put together an overall project plan that includes handling existing apps. My working guess is that the new system will be sufficiently different that we won’t be able to seamlessly upgrade behind the scenes, so we’ll likely support both the old and new system, and provide a way of upgrading old apps (likely a page at a time) to the new system, which will require some manual inspection of the output to make sure it works the way you want it to. But, this answer is subject to change as we develop this further.


@josh I think this is great - And is on the right track. I use Bubble to build Web Apps and prefer resources being put into making it the best Web App builder possible.

The PWA route is a fantastic middle ground, in my opinion, between the Web App and Native Mobile App. I, for one, support Bubble’s direction on the matter!

1 Like

I am also supporting the PWA initiative. Great!

Thanks so much!

I agree that focusing on PWA is best moving forward to build Bubble’s niche, given the limited resources.

What could help though is having someone explain how to wrap the app, as this part is mostly left to users to figure it out.