This is our August community update; you can read July’s update here.
Thank you so much to everyone who helped spread the word, whether by retweeting, sharing on LinkedIn, or just telling a friend. Helping no-code succeed is a communal effort, and it’s a virtuous cycle: the more people we bring into the fold, the more robust the ecosystem and our platform can become, which brings in even more people. Our goal is to flip from a world where coding is the default starting point for software development to one where most software starts as no-code. We’re making real progress towards that tipping point, and the more hype we can generate around Bubble, our users, and the no-code community in general, the sooner we’ll get there.
We are already spending the money, mainly on hiring. We’ve been almost comically short-staffed for most of our existence as a company. That forced us to stay efficient, goal-oriented, and very close to our users and community, all of which we want to keep. But it’s also a blocker for making the kinds of revolutionary changes we want to make: frankly, making deep tech investments in our infrastructure while simultaneously adding features, fixing bugs, and staying responsive to our users is a lot of work and for the last few years we’ve been moving more slowly on every front than we’d like to be.
On that note, we have a lot of people to welcome to the team this month:
- Shogo and Sravani joined our engineering team
- Grace joined our product team
- Katherine joined as our chief-of-staff
- Nichole joined our growth team to lead our Immerse program
- …and tomorrow, Niki and Bhavika start on our success team, and Ian joins engineering!
If you’re interested in joining us, you can browse our list of open roles. For Bubble power users, we especially want to call attention to our success positions (continental US and western Europe). We consider previous Bubble experience a plus for any of our open roles, but it’s especially valuable on the success team, where you’ll be helping other members of the community learn Bubble and solve their problems.
Changes we made this month
We shipped a number of small product improvements:
- When evaluating “and” or “or” expressions, we avoid unnecessarily evaluating the second half if we know the answer from the first half.
- It’s now easier to debug capacity consumption: clicking on a point on the “Periods where the app hit its maximum capacity” chart will bring up a donut to allow drilling in on what was going on in that time period.
- We’ve updated many of the in-editor instructional videos (many of the old ones dated back years)
- We’ve continued to release bug fixes to version control, as well as showing more detailed descriptions of conflicts to make it easier to understand them
- We added a “:formatted as JSON-safe” operator to make it easier to build API calls that require encoding data as JSON
- We added an “Arbitrary Text” data source to make it easier to build dynamic expressions that start from a chunk of text
- We made some more changes to the way we process API data to improve performance of API calls
We also added two new pages to our own website:
- bubble.io/security: goes over frequently-asked questions about our security infrastructure and the way we protect data
- bubble.io/diversity: our stance on diversity, equity, and inclusion at Bubble
A few things to check out on our blog:
- Sixteen new App of the Day posts
- A profile of one of our amazing bootcamp instructors, Ryan Badger
- And if the Olympics have you in a sporting mood, you might be excited to learn that the International Tennis Federation uses Bubble!
This month in numbers
Total number of conversations via bug reports or [email protected]: 6,331 (up 3.6%). Note: last month we reporting over 11,000: we think this was an issue with the analytics tool we’re using.
Total received messages: 10,461 (down 0.7%)
Average response time to messages: (1h 44m during business hours, down 8.2%)
Time to resolve bug reports escalated to the engineering team: the average lifespan of open bugs and bugs resolved in the last month is 6.2 days (down from 3.0). This is way up from last month because we had an issue with our ticketing system that was causing some tickets not to get tracked properly, leading to delays in our response time
Things on our minds
Coming out of the fundraising round, we’re focused on execution, execution, and more execution. We have a lot of work to do to hit the ambitious goals we have for ourselves, and between hiring, on-boarding, and driving products forward, it’s a busy time.
This was not a great month for reliability: we had a few outages, as well as some code releases that had to be quickly hot-fixed because they were breaking some user apps. The longest outage was due to an DDoS attack on our systems, which we believe was motivated by an attempt at getting ransom: our engineering team was able to block the attack fairly quickly, and we learned some things and made some code changes that should help us respond even faster in the future if we get attacked again.
One way we may be able to effectively spend our new cash for short-term reliability wins is on QA: we’re exploring some options for outsourced QA that could potentially quickly move the needle on how much breaking code makes it to production.
What we’re currently working on
Our focus for this quarter is performance, and we’re doing a bunch of investigation and research to figure out where and how to invest to have the biggest impact, which will lead to spinning off new projects. We’re trying to be a bit more “measure twice, cut once” about this than we’ve been in the past, so want to make sure we’ve picked the right set of benchmarks and metrics to maximize how much our work leads to important, user-facing improvements.
Updates on our ongoing initiatives:
Version control reliability: as mentioned above, we released some fixes and improvements, and we expect to release more fixes this month as well.
Migrating some of our code to Typescript: we’re still targeting end-of-summer for this
SelectPDF replacement: still on ice for now.
New responsive design engine: as mentioned in our last update, we stretched the timeline to make some improvements to the approach. We’re making good headway executing against the revised plan. It’s going to be worth the wait!
The complete redesign of our editor is still in testing and bug fixing mode. We’ve been having the whole team use it internally, and have uncovered a bunch more issues in the process. In contrast to the new responsive design engine, I want to temper expectations here: we’re trying to strike the right balance between getting something shipped soon, and making sure what we ship is high enough quality that it’s viewed as a net improvement.
Bootcamps: our first cohort of students graduated from the Professionals bootcamp, and we’re excited to see the projects they work on for others in the community!
It’s definitely a new era in Bubble-land: thank you all for coming on the journey with us!
Josh and Emmanuel