I built a Flutter + Supabase app to fix pickup football in Tunisia 8 sessions in, here's what I learned
For context: organizing a pickup football game in Tunisia
means sending a WhatsApp message, watching it get buried,
half the people confirm and don't show up, and the game
gets cancelled because you never had enough players.
This happened to me one too many times. So I built Kawer.
The idea is simple — open the app, see games near you,
join with one tap. Or post your own and let people find
you. No group chats. No chasing confirmations.
What's actually working right now:
- Browse games near you (PostGIS + Supabase RPC)
- Join / leave a game
- Post a game with a full map location picker
- Private crews with invite codes
- Show-up rate — if you confirm and don't show,
your reputation takes a hit
- WhatsApp share for games
- Landing page live
- Play Store listing ready
Stack: Flutter + Supabase + PostGIS for location queries.
Zero backend code written — the whole server side is SQL
functions and RLS policies. One RPC call returns nearby
games ordered by start time. Honestly felt wrong how easy
it was.
Where it actually stands: me and a few friends testing it.
Real users coming this week. I genuinely don't know what's
broken yet until real people touch it.
What I'm building next: push notifications via Supabase
Edge Functions + FCM when a game near you is filling up.
Honest questions I'd love feedback on:
Show-up rate as a reputation system — good idea or
will it kill adoption because people feel judged?
Private crews — is this a distraction from the core
or does it make the product stickier?
Anyone built FCM + Supabase Edge Functions before?
What broke?
Happy to answer anything about the stack or the build
process.