Community systems · Shipped
HALO, a carpool a community runs itself
A rides app for parents, drivers and community admins, with an operations console for the people who are responsible when something goes wrong.
Flutter, Dart ·
What it found
Trust is the product, not routing. No community would adopt the app until the admin console existed, so the thing that looked like back-office tooling was actually the feature.
- 3distinct audiences in one app
The work
What was actually built
A community that already shares school runs does not need a marketplace. It needs the arrangement it already has, written down, with the awkward parts handled: who is insured, who is approved, and what happens when somebody cancels at seven in the morning.
So HALO is two products. A Flutter app for the people in the car, and a separate operations console for the handful of people accountable for the network's safety. The console shipped first, which was not the plan.
It is live at halorides.app.
Still open
What this did not settle.
Does it work for a community that was not already coordinating?
Every group so far began with a shared group chat and existing habits. A community without that may need the product to create the trust rather than record it, which is a different and harder claim.
Who carries the liability at scale?
At one community the answer is the community. That does not obviously generalise, and it is a legal question before it is an engineering one.
See it
Open it, or read the code.
halorides.app. Opens in a new tab on an external site.