Hi all,
Sorry for the slightly delayed update – the 1st fell on a Sunday this month, so I decided to bump the update to Monday. You can read the prior update here: Monthly Community Update -- October 2020
This month, like last month, is light on product updates: most of our engineering team has been focused longer-term investments in our infrastructure and code, including multi-month projects, bug fixing, and stability improvements. While not all of this work is highly visible, it pays off in terms of platform stability, and is necessary groundwork to continue to scale with our community. On that note, our community-building and educational projects have made a lot of headway this month, and we’ve been excited to see the impact.
Changes we made this month
On the community-building front:
-
The immerse program has started with 10 people in the first cohort. We are excited to use our technology to help making entrepreneurship more inclusive and open. To get this launched, Yaw on our team processed more than 600 applications and conducted tens of interviews.
-
We’ve launched two live webinars: “Intro to Bubble” and “Office Hours”. The Intro webinar is designed for new users, and runs every Tuesday at 11am. We give folks a rundown of the editor, do a live build of an app, and open it up to Q&A at the end. Office hours are every Thursday at 11 am: we use Zoom breakout rooms to group people together to create a collaborative environment where people trade notes and get live help from other users. Our team bounces around the breakout rooms to provide additional help as well. We’re excited about the opportunity to build community, deliver live support and training, and increase overall success on Bubble.
-
After years of having a fairly boring Twitter account, we’re now posting actively. Twitter is where a large chunk of the no-code community hangs out, and we’re excited to have more of a presence. Support us at twitter.com/bubble!
-
We’ve been partnering with more colleges to use Bubble as a teaching tool, including a course at Stanford in January, and a workshop at Yale over winter break taught by @gregjohnkeegan.
-
We’ve partnered with OnDeck to be the primary platform for their No-Code Fellowship.
-
We’ve continued our App of the Day series with 19 new posts!
On the product front, as mentioned, this was a modest month, but we’re excited to launch an idea board for upvoting feature requests. This has happened informally on the forum, but it’s hard for us to quantify the degree of interest in any particular feature, since there’s no clear “click here to vote for this”. Bonus: if you vote for a feature, we’ll notify you when we build it! In addition to the idea board:
-
We made some upgrades to our primary Redis caching cluster that led to significant performance improvements in how fast it is to retrieve cached data: these improvements have a small but noticeable impact on a large variety of different Bubble operations.
-
We rolled out an internal project to provide real-time feedback to the engineering team on code quality, which should accelerate our efforts to improve our codebase. Investing in the quality of our codebase is a long-term bet that leads to faster time to deliver features in the future, and fewer bugs.
On the team front, we’re pleased to welcome Gerry to the engineering team, who’s taking time off school to intern with us.
This month in numbers
-
Total customers who reached out to us through bug reports or support@bubble.io: 3,881 (up from 2,540 last month)
-
Total received messages: 6,821 (up from 6,805 last month)
-
Average response time to messages: (3h 15m during business hours, up from 3h 00m last month)
-
Time to resolve bug reports escalated to the engineering team: for bugs resolved in the last 30 days, it took on average 7.0 days for engineers to investigate and deploy a fix or find a workaround for the customer. (Note that while we’ve tracked this metric in the past, the way we were calculating it wasn’t taking into account bugs that were opened prior to the last 30 days: we changed the methodology this month to more accurately reflect the average customer experience)
Things on our minds
This has been a good month for overall stability compared to the last few months. We’ve had less downtime and fewer bad code rollouts, as well as seeing fewer bug reports that needed escalation to engineering. It’s gratifying to see the focus and investment on this pay off. We’ve been turning our attention to some of the more infrequent, harder-to-reproduce bugs that are sometimes reported: these bugs tend to have the biggest impact on apps with the most users, since while they tend not to be noticeable at small scales, at larger scales they crop up often enough that they can be disruptive for our biggest users. These bugs tend to be particularly difficult to track down: usually it’s a cycle involving us deploying logging, waiting for the bug to occur again, examining the logs, and repeating until we’ve narrowed it down. But it’s satisfying that we’ve been able to clear out the incoming bug queue enough to give at least some of these bugs the attention they deserve.
Version control remains a reliability hot spot – we still get regular version control bug reports – but we’ve resolved the staffing issues I mentioned in the last update, and are now making progress again on cleaning up the various causes of problems.
On the team front, we’re continuing to professionalize and specialize. On our success team, we’ve created a specific team of “Bubble engineers” responsible for triaging bug reports, and on our engineering team, we have a team responsible for handling escalations. We’re continuing to aggressively hire on both teams, and we’re looking to bring in a VP of Engineering to lead our organization-building efforts, since we’re reaching the point in our evolution where we’re ready to bring on experienced senior leadership. As I mentioned in the last update, the investment in this kind of team-building shows up as a short-term burden on our staffing, but the long term impact is that we can achieve levels of quality across the board that it’s just impossible to do at our scale with a ten person engineering team.
What we’re currently working on
New initiatives since the last update:
- We’re building a CRM (using Bubble, of course) to help our success team create ongoing context about users and their apps. One of the things I love about working at Bubble is how well our team knows our users, and as we get bigger we want to make sure we capture and share that knowledge across the team, since it’s often much easier to help someone quickly if we’re already up to speed on what they’re trying to do and what issues they’ve had in the past.
Updates on our ongoing initiatives:
-
We now have a working prototype of a potential direction for the new responsive engine, and we’re in the process of gathering feedback on it to confirm if that’s the direction we want to go in.
-
We broke ground on merging the Bubble reference into the manual to create a unified experience for our written documentation: we now have some in-editor links going to the manual instead of to the reference, and will be shifting more of them over as we move content to the manual.
-
Moving more of our asset-building to the new system is alive again: we’ve ramped up a new engineer onto the project and he’s been starting to move things over. Each asset we move over eliminates a potential version-control bug, so excited to see the progress resume.
-
Moving apps between different databases is still on pause, but we’re starting to put in place the team to work on it and expect it to start moving again once another project wraps up.
-
Splitting the main cluster into two release tiers, Immediate and Scheduled, is behind our initial estimated release last month because we ran into some unexpected technical complexity, but we’ve worked through the complexity and the project is moving again.
-
Our Zapier plugin is now going through Zapier’s approval process, and we’ll release it as soon as that’s complete!
-
The complete redesign of our editor continues to make good progress. A couple people on the team are still working on the initial build-out (we’re wrapping up work on the Plugins and Logs tabs), but we’re starting to transition other people to the next stage, which is cleaning up smaller details and building tests.
-
Hiring: we are actively looking for designers, engineers, product managers, and members of the Success team!
-
We’re also looking for more experienced bubblers to be bootcamp instructors
Best wishes to everyone, and hope you all have a happy and healthy November,
Josh and Emmanuel
Doing great!
