Totally agree with bug reports!
I honestly don’t bother to report some editor bugs anymore 😮💨
I just refresh the page and hope it won’t appear again, but I have seen some they keep popping out.
I did saw some improvements on the amount of times the editor crashes after they released a fix for it though 
Strong +1 on that. Reporting bugs is a futile and cumbersome exercise. In addition to cumbersomeness of posting, we need to break our heads and spend hours to explain and reproduce the bug for the team just to hear “It is intentional” or “Since you can’t tell us how to reproduce this, it is not happening”.
Once Bubble support team even asked me to share a screen recording of editor crashing in the browser, else they won’t believe it was crashing even when I sent a screenshot of when it crashed. Now how does one send a screen recording of crashing? As if we are supposed to keep our screen recording on all the time.
And many bugs are just plain silly to be able to write down and explain. And they just happen randomly.
Many times I also feel like Bubble should have a bug bounty or some kind of reward for us to be spending hours in reporting bugs, preparing specific pages to show reproduction of bugs, explain bugs, convincing to the team on the bug. Bubble just seems to plainly ignore the effort there.
Since September 13, 2021 I have submitted more than 120 Bug reports. I know this because I have 119 videos in my loom Bubble Bug Folder, and not all bug reports I submit do I make a video for.
I’d say 25 - 30% of them are me with tired eyes not spotting my mistake. One out of three reported recently was just that.
If I were to assume that each Bug report that I could say was not due to my mistake and was an actual Bug, or what was determined as ‘expected behavior and I should post an idea to the ideaboard’ takes me on average of 15 minutes to make the video, load video to loom, fill out Bug report than that would be about 21 hours of my time over the past 2 years…Keep in mind, that does not include the time it takes to review Bubble support emails, re-explain via email the bug reported, educate support on how Bubble works ( sometimes it takes multiple emails to have support accept the behavior as a bug ) and why what I am reporting is a bug, and then to check if the bug has been fixed once support emails to confirm a fix has been implemented (if they do).
The fact that the Bug tracker, where we can see the status of all the bugs we have lodged had been removed sometime ago, makes it even more cumbersome to keep track of all the bugs ourselves, so that we can send emails to request updates or to see if any movement has been made. I’ve had a considerable number of reports ‘slip through the cracks’ and take a month or more before any fix has been implemented.
Support has a very tough job, and I do not think the issues/frustrations with the system are because of the support staff.
Couple of things that take time other than what you have mentioned are:
These two take away a lot of time as debugging and simplification are difficult jobs.
And I am still leaving out the inconvenience caused by the bugs to our customers, and its effects (Our support team, operations etc.).
So what you say is 21 hours, would surely be a good multiple of that in real.
is it possible to become part of the beta of the table element? i am working on a new product that would highly rely on this feature @josh
Yes, true. I also didn’t incorporate the time of having to test the ‘solution’ that support offers (which 9/10 times seems they didn’t test before spitballing it as a solution) to then have to make another video demonstrating the solution they suggested doesn’t work and to please focus on getting a bug fix.
Hi Josh,
That was again a productive month.
Of course I can spend my valuable time giving you feedback, but can you guys also respond to that feedback? The lack of a detailed response to the community feedback about the new pricing model and the huge amount of feature requests not being addressed make me hesitate spending that time a bit.
Some of your fastest growing competitors use Discord to keep in touch with their communties (and respond to feedback), is that something you girls/guys consider?
@ZubairLK I have experienced significant speed issues with a client between Starter and Growth even though the total WUs fall below the Starter capacity.
That sounds impossible on WU metrics? Strange…
On capacity it made sense. But between WU plans, the speed should be the same? @josh
Thanks
Zubair
Agree - went back and forth with support and got non-descript answers back, unfortunately. I ended up giving up and paid for the higher plan to keep the customer happy.
Note - this is a sub-app deployed under a Team plan and I see noticeable performance differences between the same app running on Team/Growth/Starter plans even though they are identical.
All great stuff, thanks!
