Thanks for the response @emmanuel. It’s clear as usual that you do listen to your community, and I think everyone appreciates the fact that this discussion can be had at all. While I was as surprised by this message as anyone, I still think the continued discussion and your response is very much in line with the transparency we’ve seen in the past.
I also think your previous response changed the tone of the conversation in a more productive way and several users have made good suggestions on how an alternative price structure could look.
I’ll still share my five cents on what occurred today though, as I think this runs deeper than simply a miscalculation on the specifics of the plan.
From a communication standpoint, I think this should have been done in a different way. I honestly found it obvious that this would be a hugely unpopular change the second I read your initial post, and was not at all surprised to see that the comments were flooded with negative responses to the point where the forum crashed. My thoughts were that you were either simply prepared (for internal reasons unknown to us) to weather the storm and push through a predictably unpopular decision no matter what, or that you genuinely (but surprisingly) were caught off guard at just how negative the feedback was. With your later posts, where you show more openness to listen and alter the decision based on the feedback, I can’t help but think that communicating it both via the forum and through an email newsletter was a mistake. A change this massive obviously deserved more research.
The reason I say this is that I think you underestimate just how much reputational damage you can do by appearing so unpredictable: you’re giving the impression that the rug can be pulled out from under long-time users from one day to the next. I’ve given this same feedback to your customer support team a few times actually: you’re always transparent, helpful and positive but I’m sometimes taken aback at how casually you approach issues that are of huge consequence to your User’s projects and the relationship they have with their clients. Bubble has come a long way in being taken seriously as a long-term application building framework, but missteps like this are a step back. I’ve already received a handful of emails from clients concerned about the change, and I’m not too happy that this was simply pushed out with no warning whatsoever - the fact that an agency and its clients receives this message at the same time does not exactly put us in a flattering position.
I think this message has put some major concerns into the minds of your Users as to what kind of limitations or price increases are introduced next - and rightly so. I say this as a long-time and loyal proponent who has stayed quiet or defended more or less every one of your previous decisions over the years. Even I am starting to feel uncomfortable at just how much trust we’re placing in one platform that’s now giving the impression that it can radically change overnight. I’m not principally against your lock-in strategy (I don’t think we would have Bubble without it), but it’s a source of concern when it’s coupled with frequent and unpredictable changes to its fundamental structure and pricing. I don’t think it’s an exaggeration that you made a serious dent in the trust of a lot of Users today.
I won’t comment too much on the plan itself as you’ve already addressed that the change won’t go through as initially sketched out… suffice to say that I too agree that the numbers seem both arbitrary and absurdly low and places terrible incentives on developers to find hacky ways of circumventing the limitations. There are plenty of good arguments already, so I’ll leave it at that.
Still, I think you should take seriously that this has caused a fairly unhealthy stir in the community that has rattled many long-time users and their clients. I can’t help but question exactly what kind of process was behind this change in the first place? Was the universally negative response really unexpected? It almost beggars belief to be honest.
While I appreciate your response, it also feels like we’ve been here before, more than once. I really wish these kinds of processes were not made as public and sudden as this. I think this deserves a proper post mortem and not just an adjustment to the plan.
“Move fast and break stuff” may work for Facebook, but it’s not gonna cut it for a platform like Bubble.