Next Door · Case study
Thanks for Visiting
Reach out

Context
The short version · ~12 min read
You know every face on your floor. Do you know one name?
The problem was never distance. The apps built for streets turned them into public feeds with ads in them, so the real conversation moved to a group chat nobody can search and everybody mutes.
My process went from 20 conversations in my own building to 4 decisions that all protect the same promise, and ended on 1 calm place for 1 building. The output is 3 surfaces of a single web app, chat, events and a marketplace, sharing one member list and one login, running inside free tiers with the code there to fork. The outcome has not happened yet: no street is living on it, because it is a demo rather than a launch.
- 3 surfaces
- chat, events and a marketplace, sharing one member list and one login
- 30 tables
- the schema behind live messages, RSVPs, listings and their histories
- Guest or Google
- walk in with no account at all, or sign in and keep a profile


02
Background and process
From Locked In to a Chain I Own
Every link in that chain is one I can pull out. The database, the host, the mail, the editor: each is a piece doing one job, and each has a replacement I could move to in an afternoon without touching the other six.
The first version of Next Door was generated on a vibe coding platform, and running it meant staying there. Rebuilding it across tools I picked myself is what turned a product I rented into one I own.
The process, in 15 steps
Open the at the top of the screen to jump between steps at any time.
Problem
Research, insights and personas
03
Problem statement
Distance is not the broken part. A building already puts everyone within a floor of each other.
The apps built for streets turned them into public feeds with ads in them, so the real conversation moved to a group chat, which nobody can search and everybody mutes.
04
Research
20 conversations in my own building first, then desk research: how well people know their neighbours, what pays for the apps built for them, and what happens to group chats.
20 neighbours
People in my building wanted to start groups and get things going, but didn't know where to start.
My conversations
26%
Only about a quarter of US adults know all or most of their neighbours, down from 31% in 2018.
Paid for by ads
Nextdoor Holdings, annual report for 2024
“We currently generate substantially all of our revenue from advertising.”
Group chats get muted
In a survey of 1,005 Americans, 75% mute group chats that annoy them and 66% feel overwhelmed by them.
- 75% mute
- 66% overwhelmed
- 55% have left 1
05
Key insights
01
Wanting isn't starting
My neighbours wanted groups and plans. What stopped them was not knowing where to begin.
02
Faces without names
Most people know only some of their neighbours. A building full of strangers needs names before it needs features.
03
Ads change the room
The big app for neighbours is paid for by advertising, so the street is the audience as much as the community.
04
Chat buries plans
Busy group chats get muted. A plan posted in one sinks under everything that comes after it.
06
Personas
Proto-personas, built from my 20 conversations, the research and what Next Door does. Composites, not real people.
- Events
- The chat
- Goal
- Start a potluck for the floor and see who is coming.
- Frustration
- She doesn't know where to start, and a message in the group chat sinks.
Next Door for them1 form for an event, with its own chat
- The chat
- Members
- Goal
- Put names to the faces he passes on the stairs.
- Frustration
- He won't make an account just to look around.
Next Door for themGuest Access, and a room number on every name
- Requests
- Notifications
- Goal
- Borrow a ladder this weekend without asking door to door.
- Frustration
- She muted the building's group chat months ago.
Next Door for themQuick Requests, where neighbours tap I Can Help
07
How might we
How might we help neighbours in 1 building start things together, without a public feed, ads or a group chat that buries every plan?
Process
Requirements to iteration
08
Design requirements
Each insight became something the design had to do. The 4 decisions further down are how each one got met.
09
IA and user flow
Where everything lives first: Next Door's 3 surfaces, what sits in each, and the 1 database they all read. Then the 2 flows that matter: joining from a neighbour's link, and Asha starting a potluck.
Information architecture
- Start
- Action or screen
- Decision
- Done
- Loop back
Joining
Asha's potluck
10
Design decisions
Every one of these traded something away to keep one promise: that a neighbour can get in without an account, and the street's messages stay in a database the street owns.
How many apps a street needs
Not taken
3 apps, one per job
Shipped
3 surfaces of 1 web app
How I got there
Three things happen on a street: people talk, people organise, people pass things along. Build them as three apps and nobody installs the second one.
What it cost
- User
- No push. A parcel at the door is a notification or it is nothing.
- Technical
- 54 components carrying 3 surfaces, so a change lands in 3 places at once.
- Business
- Nothing to install, which is the only reason someone opens it twice.
What it costs to walk in
Not taken
Sign up before you see anything
Shipped
Guest, or Google
How I got there
The person this is built for joined from a text message from a neighbour. A sign-up form is the point at which that person closes the tab.
What it cost
- User
- A guest keeps nothing. Close the tab and the profile was never there.
- Technical
- 2 identity paths through every route and every permission check.
- Business
- Guests leave no profile, so there is no member list to grow.
Who holds the messages
Not taken
One hosted service for every street
Shipped
You run your own copy
How I got there
An app whose whole argument is that your messages should not live inside somebody else's platform cannot then be somebody else's platform.
What it cost
- User
- Standing one up means Supabase, OAuth credentials and 3 cron jobs.
- Technical
- Every choice has to stay inside a free tier or the instruction is not real.
- Business
- There is no hosted product here, so there is nothing to charge for.
What the browser is allowed to ask
Not taken
The client reads the database directly
Shipped
84 routes, 1 per read and write
How I got there
Anything the browser can query directly is a privacy promise I would be asking a street to take on trust. A route is the same promise written where it can be checked.
What it cost
- User
- Nothing visible, and that is the whole point of it.
- Technical
- 84 routes to maintain, and a feature is a route before it is a screen.
- Business
- The claim is enforced in code rather than made in copy.
11
Evaluation
Tested against 10 heuristics
Before a usability study, a review against Nielsen's 10 usability heuristics.
8 met · 2 partly
Visibility of system status
Typing, read receipts and unread counts on every chat.
Match with the real world
Rooms, potlucks and House Full read like a building, but every event time is in GMT.
User control and freedom
Skip on the welcome cards; leave any event or request.
Consistency and standards
Events and requests work alike: a card in the chat, a private chat, a history.
Error prevention
Leaving, deleting and completing all ask first.
Recognition over recall
An avatar, a name and a room number on every message.
Flexibility and efficiency
@mentions, swipe to reply, double tap to react.
Minimalist design
The header is 3 icons and a menu, and each surface does 1 job.
Recovering from errors
Failed edits and uploads end in a browser alert, with no retry.
Help and documentation
5 welcome cards, and How This Works on events and requests.
12
Iteration
What broke, and what changed
From the first build to the latest, 12 April to 11 October, from the git history.
Output
The product and its system
13
The final product
One Web App, Every Device
Three things happen on a street: people talk, people organise, and people pass things along. Build them as three apps and nobody installs the second one, so they are three surfaces of one web app instead, sharing a member list, a login and a set of notifications. There is nothing to install at any size, which is the only reason a neighbour who joined from a text message ever opens it twice.
Move around in it
Willow Court
powered by Next Door
Today
Priya
14:02
14:04 · Read
Sam
14:09
Chat. The ground floor. One thread for the whole building, with pinned messages, reactions and read receipts. On a wide screen the member list comes in beside it rather than over it.
Every screen, every size
The same three surfaces, laid out for the thing in your hand and the thing on your desk.




Phone first, because a neighbour reads this standing in a lift. One column, thumb-reachable, the composer pinned to the bottom.
14
Keeping its promises
An app that asks a building to trust it with its conversations has to keep its own promises.
Private by design
No ads and no public feed. Every read and write goes through a route, and the building can run its own copy.
Built on its own system
1 palette drawn for light and dark together, with Outfit for type, so it reads the same at midnight as at lunch.
One System, Two Modes
A basic preview of Next Door's design system: the colours in both modes, the type, the icons, the cards and the logo it is built on.
A neighbourhood app gets opened last thing at night as often as it does at lunch. Dark mode as an afterthought means inverting a palette and hoping, so both modes were drawn together: two grounds, one identity, and a primary that changes value between them because no single green is readable on both.
Light mode
Pine carries the primary on white: type, icons, active states, the deep end of every gradient. Mint measures about 1.3 to 1 against this background, so it never holds a word here, only the bright end of a fill.
Dark mode
The two change places. Pine falls to about 2 to 1 on this ground, so mint takes the primary and pine becomes the depth under it. Same pair, same gradient, one value swapped, which is the whole of what supporting two modes costs when both were drawn at once.
Typography
Outfit
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789
The product's face, and the only one inside the app. A geometric sans with enough warmth to read as a neighbour rather than a utility, at every size from a timestamp to a screen title.
Icons & Cards
The two colour bands above are a claim. This is where it can be checked: one switch, the same fourteen icons and the same two cards, redrawn on the other ground with only the primary changing value.
Summer courtyard barbecue
Created by Priya, Flat 4B
The card is an invitation. The action is Join, and the rows say when, where and how full.
Borrow a drill for an hour
2h agoPutting up a shelf this evening and mine has finally given up. Happy to return it the same night, and I will bring biscuits.
Somebody else's request, not a listing. No price anywhere, and the action is I can help.

Outcome
What changed, and what is next
Where It Stands
It runs. It is a demo rather than a launch: anyone can walk in as a guest, the sample data resets on a schedule, and no street is living on it yet. What is finished is the hard part, which is the whole product working end to end for one neighbourhood.
- Surfaces
- 3
- Tables
- 30
- API routes
- 84
- Components
- 54
- Commits
- 107
- Running cost
- Free tier
Chat, events and a marketplace, on one member list.
Messages, reactions, reads, RSVPs, listings and their histories.
Every read and write goes through one, never straight to the client.
Built once and reused across all three surfaces.
First to latest, 7 April to 11 October 2026.
Vercel, Supabase and Google Cloud, within their free limits.
What is next
It's your time to build your community
This was my first project built with AI, and it was meant for everyone. go ahead and test the product, and if you like it, fork the project on GitHub for free.
One app, all screens


15
Reflection and next steps
What I'd carry forward
01
Own the chain
Leaving the platform it was first built on is what made it mine to change.
02
Lower the door
Guest Access lets anyone in from a link. A sign-up form is where most would stop.
03
Free has a design
Staying inside free tiers meant asking the server less and listening for signals instead.
Next steps
- 01Run it in 1 real building, to see which half nobody needs.
- 02Make setting up a copy a few clicks, not a README.
- 03Add push notifications, so a parcel at the door reaches someone.
- 04Run a usability study, and close the 2 heuristics only partly met.
Guest access. No account, no email.
Try it
Great products happen when the right people meet.
Let's work together
