Industry
Social
Case Study
Social Platform
You sign up, see a blank feed, close the app. At brigit.dev we built around daily prompts and pairing two people around a question. Small groups have something to do before anyone posts. One community's been using it since launch.
Project Overview
New social apps die on day one because there's nothing to do. You sign up, see a blank feed, close the app. I worked on a product at brigit.dev built around small communities, each with its own prompts, pairings, and recurring content, so people have a reason to show up before anyone posts anything.
A real community has been using it since launch. Not fake users. Not a demo.
Social app where small communities have something to do on day one, not an empty feed waiting for posts.
Services
- UX/UI Design
- Web Development
- Product Strategy
- Mobile Development
Key Deliverables
- Responsive Design
- Custom Development
- User Experience Improvements
Platform Type
Web & Mobile Platform
Tech Stack
- TypeScript
- Next.js
- React Native
- Expo
- Hono
- tRPC
- PostgreSQL
- Drizzle ORM
The Challenge
Most social products need content before they feel alive. But you need users to create content. So nobody stays long enough to create it. That's the loop that kills most apps in week one.
The fix isn't growth hacking. It's giving people something to do the moment they open the app.
Approach
Each community is its own thing, not one global feed. Daily prompts give people a question to answer. Pairing connects two people around that question so it's not shouting into a void. Recurring content (weekly check-ins, etc.) makes the community look active even when posting is slow.
I built web and mobile together so neither felt like the main app and the other felt like an afterthought. Same backend, same data, same experience.
The Solution
On mobile, you open the app, see today's prompt, write your answer, read your paired partner's response. That's the daily loop. No infinite scroll of strangers.
On web, community organizers see who's active, how prompts are going, who's been paired with whom. Light metrics, not a analytics suite, just enough to know the community is alive.
Communities feel occupied from day one because the product brings the structure. People don't have to invent reasons to interact.
Key Challenges
-
making daily prompts and pairings feel natural, not like a forced corporate wellness exercise
-
web and mobile showing the same thing without one of them lagging behind
-
pairing logic that stays fair and doesn't feel creepy, like random matching apps
-
growing to more communities without losing the small-group feeling that makes prompts work
The Outcome
People participate from day one because the app gives them something to do, not because they waited for content to appear.
A real group uses it. That's the result I care about, not signup numbers on a slide deck.
Context
Built at brigit.dev. The bet was on small communities, not a global feed. Prompts and pairings only work when there's context. A feed of everyone everywhere has no context.
Pairing was the hardest UX problem. It has to feel worth opening the app for, without the weirdness of being matched with a stranger for no reason.