New App New bugs

Morning everyone. I wanted to give you an update on the state of play with the current app. The experience many of you are having, is not what we want and not what we anticipated. I’m not going to make any excuses on that front, but I want to give you an understanding of why we released what we did.

Most if not all early stage products are built in a minimal viable way, so that you can deliver something and test with the market quickly. The back end that powers Tally was not only no longer fit for purpose and it was massively slowing us down. We’ve had to rebuild the whole back end and the front end that harnesses it.

The back end had got to a point where it was damaging us more than anticipated. Something that as a user you wouldn’t notice but we wanted to mitigate against users experiencing. We had no choice but to switch this on early last week. We test our back end services rigorously to ensure that they are secure and powerful enough. This is where most of our testing goes as this is the foundation of Tally.

We then test across a multitude of devices spread across Android and iOS, though as you may not be aware, Android is complex with various OS sitting on top of it. So why not role out and test with a cohort of users? Simply put if we had we would still be on the legacy back end system, which would not be ideal at all.

This back end release means that we can debug quicker, release sooner and develop features faster. I know we still have some pretty buggy experiences out there but the team are working evenings and weekends to resolve.

This might not feel like it yet, but this new App (front end) and API (back end) combined, is a far safer and better Tally that will be packed with the features our users need in no time.

3 Likes