Development update: when technology stays in the background

Since the last update, we have deliberately spent less time on the kind of work that adds one more flashy button, and more on the situations that really matter during a rehearsal or service: an unreliable connection, a phone put aside, a tab left open, or two leaders responding at the same time. It is harder to notice from the outside, but these details create the calm of technology that does not demand attention.

A good example is Music Director mode. When two people took on the leader role at the same time, the system could previously remain in an uncertain state. Now a clear rule, identical on every device, resolves the conflict, and we test it in multi-browser situations with tabs sent to the background. The same thinking guided the ChordPro editor's error handling and the iPhone offline-storage fix: it is better to receive a clear response than an unexpected error just before starting.

We also improved how faithfully the app reflects what happens in a community. On completed setlists, you can now mark which songs were actually sung, so statistics and licence reports do not have to guess. Missing event responses are easier to find, and Songs and Setlists are now a natural starting point for every team member.

In recent weeks we have added new languages and song sources while learning from bug reports, Sentry and direct feedback. The most important lesson for me is that an app like this is not decided in the moment of a demo, but in the most inconvenient real-life situations. That is why every improvement still comes with one question: does it stay calm enough when you want to focus on the music?