Thank you for the thoughtful reply,
My point is this: when Bunpro released the UI update, just leave it as is, for at least a period of 1-2 weeks. Let people take time to digest the update, and let the feedback roll in after a reasonable period of time. I don’t find it reasonable that they issued an update, however minor it may be in 24 hours.
The reason why I think it is unreasonable, is that it undermines the original planning put into it, and makes me question how much planning was put into it in the first place if they are willing to change that fast.
Agreed. I am not sure what the technical reasons @veritas_nz mentioned, and I would love to know specifically why, as it could impact future Bunpro updates.
Agreed. @Daru @veritas_nz @Jake and whoever was directly responsible for the updates for Bunpro should be praised as it’s so much of an improvement since I started the service.
I don’t want to have a potential misconception, but I am not doomsaying, I am saying this as a very careful observer of the forums and as someone who has paid attention to what the developers have done in the past two years when it comes to updates. It’s a huge benefit to be agile, and I think they just crossed the line.
To put it in an analogy, they are putting out the fires, but they aren’t doing anything to stop the fires from existing in the first place.
That proactive VS. reactive theme is big, as the startup I worked at that failed suffered from that and left the customer base confused and overall less willing to trust because of how they quickly maneuvered. The reality is that the failed startup had zero long-term vision. They had a product that was unique, and just left it as-is until competitors ate them alive.
I don’t want to say that is what Bunpro is doing, as I am not privy to what their plans are, but the parallels should be used as it least a helpful air of caution for reactivity being a supplement for lack of a long-term vision.
), so I’m not complaining.
