Questions
Mostly the awkward ones. If something here doesn't add up, that's worth telling me about.
No, and probably not later either. The app leans on Apple Intelligence — the AI built into recent iPhones — and on the syncing and notifications that come with every iPhone. Those are what let the work happen on the phone instead of on somebody's servers, and there's no equivalent to move to.
So everyone in your group needs an iPhone. That rules some groups out entirely, which is a real cost and not one I can talk my way around.
No. It works completely on an older one — every screen, every feature, nothing held back.
A newer phone adds Apple Intelligence, which saves typing rather than unlocking anything. With it, the season schedule comes off a photo of the coach's email and you can write an offer as a sentence. Without it, you type those in.
The rule I hold to is that the AI changes how information gets entered, never what can be entered. Nothing can go into your group's record that needs a new phone to create, so nobody counts for less because of what they're carrying. The parent on the oldest phone is pretty often the one who most needs rides.
Nothing much happens. Every phone in the group already has the whole record, so somebody else takes it over and you keep the same history and the same numbers.
Holding it isn't a position. It doesn't let that parent edit anything, see anything extra, or decide anything — entries are trusted because of who signed them, not because of where they came from.
Their count stays where it was and the driver's credit doesn't show up. Nothing chases them, nothing gets locked, and nobody is flagged to the rest of the group.
This is the hardest problem in the whole app, honestly. Nobody wants paperwork after a car trip, least of all at 6am, which is exactly when the app is asking. That's why it's one tap and why it's the only thing the app asks anyone to do.
A credit only moves when the parent whose kid got the ride confirms it, and every entry is signed by the phone that wrote it. A driver can't confirm their own trip. Each phone checks the signatures itself, so a bad entry gets rejected everywhere instead of turning into an argument in the group chat.
No. There's no live location in the app and there won't be — not as a setting, not as an opt-in. It knows pickup addresses and nothing about where anyone is at any moment.
A database of where children are in real time isn't something I want to be responsible for, however well-intentioned the reason for building it.
It doesn't check anyone's license, insurance or driving record. You decide who drives your child, the same way you do now when you text another parent from the parking lot.
No. They can't be bought, sold, traded or cashed out. They're a count of who's been driving, and that's the whole point of them. Nobody is charged and nobody is paid.
The app keeps working. There's no server to switch off and no subscription to lapse. The code is public under the MIT license, so your group's data stays readable by code you can hold onto, and anyone who wants to pick the project up can.
That's a good part of why it's built without a company in the path.
About a practice group's worth. It does nothing for one family and starts being useful somewhere around a dozen — you adopt it as a group, not individually.
It also assumes everyone already knows everyone, which is what lets it skip ratings, background checks, payments and dispute handling.
Soon, on the App Store. There's no mailing list to join — collecting a pile of email addresses would be the first thing here to contradict the rest of it. The code repository is the place to watch.