one backend, three products.

Bangor City 1876 is a fan-owned club run by volunteers. When we started, it needed three things at once: a new website, a club app for supporters and a way for volunteers to keep everything up to date on matchday.

The obvious approach is three separate builds. We built all three on one shared backend instead.

one place for everything

Fixtures, results, the league table, news, squads and sponsors live in one place. Post a result in the staff portal and it’s on the website and in the app at the same moment. There’s no copying things between systems, and nothing gets out of sync.

For a volunteer-run club that matters more than any feature. Nobody has time to update three things.

built for the touchline

The staff portal has a live mode made for one-handed use on the touchline: six big buttons for a goal, a card, a sub, commentary, half-time and full-time. Each tap goes straight out to supporters as a live update, in English and Welsh.

The app is built for the ground too. The signal there is poor, so it works offline and catches up when it can.

two languages, not two sites

Every page on the new website is in English and Welsh, and so is every push notification. Because the content lives in one place, the club writes each update once per language, and it appears everywhere it needs to be.

the point

One backend means the club can run its website, app and matchday updates without a developer. That was the brief: simple enough for a volunteer on matchday, complete enough that the club never needs us to change a score.