I’m not quite sure what this means, as to the use of the question mark is confusing me.
Are you asking if people are actually losing maybe 15 minutes a day? Or, are you asking if the fact that your team loses 15 minutes a day is actually a big deal or not? Or, are you stating that the fact that your team loses 15 minutes a day is not a big deal in your mind.
48 Weeks a year of work, 5 days a week of work = 240 days of work, x 15 minutes a day is 3,600 minutes a year, which is 60 hours a year. Personally, I charge $125/hour, so this 15 minutes a day would cost me $7,500 a year. Of course though there are more than just editor slow downs, so when I factor in all the time I spend trying to debug and resolve issues that I instinctively believe to be my own fault, only to uncover its a bug, and everything else related to those situations, I am losing some $15,000+ a year in productivity.
Of course things vary, so I guess if we consider a lower hourly rate of an average Bubble developer at maybe $50/hour that is $3,000 a year. Take into consideration a sense that Bubble has some 200+ agencies, we can realistically say that this 15 minutes a day loss due to slow/buggy behaviors in the editor cost an aggregate $600,000 a year across the 200 agencies.
I would prefer Bubble to pay a single engineer $300,000 a year to fix all the issues that cause this 15 minutes a day loss of productivity. But, I don’t know, that is just my opinion on how resources can be utilized more effectively. I think it is wiser to not throw resources away, which is what a 15 minute a day loss of productivity is.
I understand, from your perspective there is nothing to complain about, but trying to look at things from a different perspective, some people might see the repeated threads popping up as a sign of something is wrong that needs to be addressed.
Currently 118 respondents, with 34 saying 0 times a day…this is just under 30% of respondents. That means a bit more than 70% of respondents feel there is something that is needing to be addressed. That is not a tiny portion of users, that is a Large Majority of users who feel like some things need to be improved.
Constructive criticism always comes across as negative when the people receiving it are not open to feedback. Constructive criticism when received by those open to feedback and intent on making changes based on that feedback use it to become aware of things, they themselves, may not be aware of, and take remedial steps to address the issues raised through that constructive criticism.
I would say it may be likely that the reason for the increase recently in posts with constructive criticism and looking for other users views, is that perhaps Bubble has not been doing enough to use the constructive criticism to make the improvements in areas where the users providing the feedback view it as necessary.
I think what a lot of people miss as the main sentiment of these types of posts is that the users who are experiencing issues within the editor are demonstrating very clearly their love of the product and their goal of assisting the product team to improve it so that it can just become better for everybody. The time those users take to make these posts, to begin these discussions, to lead to tangible results that benefit the entire community should maybe be met with a little bit more of a fist bump and praise for having taken the time to attempt to advocate for the users. I can tell you, some 3-6 months ago when I was posting bemoaning posts are experiences with support emails, lots of people probably just looked at it as negativity and venting, but what it resulted in is a tangible change in the approach of how Bubble support relay information regarding bug reports, which ultimately for me, resulted in time savings and a better overall experience of submitting bug reports and communicating with support for them.
Change happens only when those in charge are made aware of the need for a change. When people sit quiet and content, nothing changes.
In the last two days I’ve lost 5 hours of productivity.
What was previously working functions of copy and paste into other apps where the option selected would have continued to be mapped properly, no longer are and the dynamic expression reads ‘current selected option is option’ where that last ‘option’ in the expression was supposed to be a specified option value like ‘read’ or ‘create’ and due to this issue, and the fact that the issue checker doesn’t pick up on those issues since the dynamic expression is still blue, I need to click into EVERY SINGLE ELEMENT to try and find ALL of the broken expressions throughout ALL of the pages and reusable elements to manually find the issue (issue checker doesn’t do it) and remap to the appropriate option while also needing in the original app reference the different elements…this alone cost me 3 hours in lost productivity.
Then today, a previously working function for a collapsed sidebar, when collapsed now the elements when hovered are flipping out and unclickable, and so after attempting 2 hours of debugging and issue resolution on my own, I had to attempt to submit a bug report only to find this nonsense going on with bug report system now.
So, should I just sit and quietly accept this loss of $625 in two days because I’m happy with what works, or should I bemoan and post about the broken things that cause these types of financial issues?
