As mentioned in previous communications, we prefer to share updates when we have something concrete to show — especially regarding the UI. The work we’re doing is massive: we are converting a 20-year-old codebase with thousands of files, many of which are highly complex. This is not just about rewriting code, but ensuring that, particularly in the engine, the new version behaves identically to the original given the same inputs.
Regarding the UI, we are actively working on it. However, progress has been delayed due to an urgent technical issue with another app we manage, which required our immediate attention. This temporarily slowed down our efforts on BuzzerBeater.
That said, we are fully committed to the project and will share progress as soon as we have something meaningful to show. It’s disappointing, though, to see that while the vast majority of users are patiently waiting and supporting us, a small group of 4–5 individuals continue to post out-of-context comments and unnecessary tags.
If you’ve tolerated the current state of BuzzerBeater for nearly two decades but suddenly feel the need to express impatience now, we kindly suggest reconsidering your approach — or your involvement — as that’s not the kind of community spirit we’re trying to foster.
Again, we’ll share an update when it’s ready. I don’t want to commit to specific dates because this is a highly complex project and unforeseen issues can arise. But when we do publish an update, we’ll make sure to highlight the immense amount of work involved so everyone can appreciate the scale of the progress.
As for the UI, we already have a few mockups of the main screens. However, we prefer to share them only once we’ve verified their feasibility in code. We don’t want to present a design that later proves to be unworkable or ends up not being used.
Thank you for your patience and understanding. I truly hope this helps avoid further speculation moving forward.