About DashHOOD

We are building the app we wanted when a plan died in a group chat for the fourth time in a month.

The problem we started from

A plan gets made across forty messages. Half the group never sees it. Nobody is sure who is actually coming, so nobody commits, and by the time someone tries to count heads the thing has quietly died. The chat was never the problem — chats are good at talking. They are just bad at holding a decision still.

What we built instead

A HOOD is a real group of people who are already near each other. Inside it, plans are first-class rather than something you scroll back to find:

• Activities have real seats and a real roster, so “who is coming” is a fact rather than a guess. When something fills up, the next person joins a waitlist.
• Rooms let a large HOOD keep its threads apart — rides, plans, gear talk — without splitting the group into four separate chats that each miss someone.
• The board holds what still matters after the conversation has scrolled past it.
• Postcards tie a photo to a place, which gives people a reason to actually go somewhere and look up.

Who we are

A small independent team — five people, two of whom write code — building this in the open on iOS and Android at the same time, against one shared backend. We started with a single campus community because that is where we were, and we are opening it up from there.

We are not venture-funded, we do not sell data, and we do not run ads. That is not a positioning statement; it is why the product can be shaped around people meeting up rather than around time spent in a feed.

How we work

Our development process is written down and public, adapted from Anthropic’s AI-native SDLC playbook. Anyone on the team can file a problem; a weekly conversation decides what becomes committed work. Small, well-bounded fixes skip all of that and ship as a pull request.

Talk to us

Bugs, feature requests, privacy questions, or a request to join the beta — support@dashhood.app. A person reads it.