Groups and invites
Private groups, invite codes, join requests an admin waves through, three member roles, and per-group house rules.
What is built
Halbreven is being built in the open by one person. This page says what actually exists, and what does not — kept accurate rather than flattering, because the second kind of page is worth nothing.
Where it stands
21sports
10playing surfaces
22screens
49database migrations
27tables, all with row-level security
The app is React Native on Expo, for iOS and Android from one codebase. The backend is Postgres on Supabase, where the access rules live.
Working today
Fixtures
One-off matches or a standing weekly schedule. Yes / maybe / no, a squad cap with an ordered queue, and a lock before kick-off.
Teams
Automatic balancing by grade and position for two to six sides, up to three simultaneous pitches, manual swaps, kit colours and keepers.
Attendance and cover
Marking who actually turned up, including when somebody was covered — by a teammate, who then gets rated, or by a guest, who does not.
Ratings
A thirty-second post-match pass, four dimensions per sport, keepers judged on keeping, shrunk toward the mean until there is enough signal.
Trust and cards
An append-only ledger, asymmetric recovery, flagging with a quorum, the mildest reading winning, a right of reply, and voiding that returns what it cost.
Timeline and chat
A group feed with photos, comments, likes and pinned posts, plus realtime chat with photos and reactions.
Stats and the season
Turnout, standings, results, a portable player profile, and a season recap that reads like a record book rather than a dashboard.
Not done yet
The honest half of the page.
- Nobody has used it. No pilot group, no public release. It has been verified by its author, not by a Sunday league.
- No app store build exists. It runs in development, and the first real build is the next piece of work.
- Push notifications are half built — the app can receive them, the server cannot yet send them.
- The rating dimensions for the newer sports are drafts. Football and basketball were thought about properly; kabaddi and korfball were chosen from a desk and want a player's eye.
Why say all that
Because a page that only lists what works is how software gets oversold, and this is a product about being honest with the people you play with. If it is going to ask a group to record who let them down, it can manage to say what it has not finished.
Who is building it
Halbreven is designed and built by Arrit Gashi. It came out of the ordinary problem of organising a weekly game and the ordinary irritation of doing it in a chat thread that forgets everything.
It is being built deliberately rather than quickly: the principles were written before the features, every non-obvious decision is recorded with the reasoning behind it, and things that break a principle get thrown away even when they work.
If you run a group that plays every week and any of this sounds like your Sunday, say hello: info@halbreven.com.