Next Door · Case study

Thanks for Visiting

Reach out

Context0%

0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
Back to overview

Next Door

A private community app for one building, block, or street

The Next Door key visual: a tablet floating among broken slabs of concrete on a dark ground, its screen showing the welcome card, Next Door, welcome to your friendly neighbourhood

Context

The short version · ~12 min read

Companydeeproduct.org
RoleDesign & Build
DeliverableZero to V1
Scope
Product designDesign systemFull-stack buildBrandLaunch

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
Next Door on a laptop: the chat at full width, one pinned message in a pill at the top, the two sides of the conversation against the left and right edges, and an event card in the thread
The same Next Door chat on a phone: one column, the pinned pill above the thread and the composer along the bottom

02

Background and process

From Locked In to a Chain I Own

Design
Figma
Build
Claude CodeVS CodeNext.jsSupabase
Ship
GitHubVercelResend

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.

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.

201831%
202526%
Pew Research Center, 2025

Paid for by ads

Nextdoor Holdings, annual report for 2024

“We currently generate substantially all of our revenue from advertising.”

SEC Form 10-K, 2025

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
Secure Data Recovery, 2023

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.

AshaWould-be organiser
  • 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

TomNew tenant
  • 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

MeiBusy parent
  • 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.

R1Start in 1 formAn event or a request is 1 form, and lands in the chat as a card.From: Wanting isn't starting
R2A name on every faceEvery profile carries a name and a room number.From: Faces without names
R3In from a linkGuest Access or Google, from the link a neighbour sent.From: Faces without names
R4Owned by the buildingNo ads and no public feed. The building runs its own copy.From: Ads change the room
R5Plans out of the noiseEach event and request gets its own chat, and ends when it is done.From: Chat buries plans

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

LEVEL 0ProductLEVEL 1SurfacesLEVEL 2Screensand partsDATASharedNext Door1 web app for 1 buildingThe chatthe whole buildingEventsplans, each with a chatQuick Requestsasks, each with a chatMessages@mentions, replies, reactionsPinned messagesEvent and request cardsMembersname and room numberSearch · NotificationsUpcoming · My EventsCreate Eventname, place, time, up to 50Event chatends 24h after the eventEvent HistoryOpen requestsNew Requestup to 3 photosRequest chatI Can HelpHistory1 database the building runsevery surface above reads the same members
  • Start
  • Action or screen
  • Decision
  • Done
  • Loop back

Joining

NOYESTaps a neighbour's linkLands on Next Doornothing to installKeep a profile?Signs in with GoogleSets up a profilename and room numberReads 5 welcome cardsor skips themGuest AccessGuest 1234, room VisitorIn the building's chat

Asha's potluck

NOYESAsha wants a potluckand doesn't know where to startOpens Events, taps +Fills in 1 formname, place, time, a limitA card lands in the chatand everyone is notifiedA neighbour taps Join EventRoom left?“House Full”the button stopsJoins the event's chatby name and roomEnds 24h after the event

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.

01

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.
02

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.
03

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.
04

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

01Met

Visibility of system status

Typing, read receipts and unread counts on every chat.

02Partly

Match with the real world

Rooms, potlucks and House Full read like a building, but every event time is in GMT.

03Met

User control and freedom

Skip on the welcome cards; leave any event or request.

04Met

Consistency and standards

Events and requests work alike: a card in the chat, a private chat, a history.

05Met

Error prevention

Leaving, deleting and completing all ask first.

06Met

Recognition over recall

An avatar, a name and a room number on every message.

07Met

Flexibility and efficiency

@mentions, swipe to reply, double tap to react.

08Met

Minimalist design

The header is 3 icons and a menu, and each surface does 1 job.

09Partly

Recovering from errors

Failed edits and uploads end in a browser alert, with no retry.

10Met

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.

12 AprCleanup jobs broke the free plan's cron limitMerged into 1 daily job
13 AprGoogle sign-in looped back to the startThe callback became its own page
6 JunGuests landed on the profile formStraight into the chat, cleared after 24h
10 OctHidden tabs kept asking the server for newsPolling pauses when a tab is idle
11 OctThe chat checked for messages every 5 secondsLive signals while it is connected
11 OctEnded events stayed until cleanup ranHidden 24h after they end

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

nextdoor.deeproduct.org

Willow Court

powered by Next Door

Pinned · Barbecue Saturday 18:30, courtyard

Today

P

Priya

Anyone free to sign for a parcel this afternoon?
👍 2

14:02

I am in all day, leave it with me.

14:04 · Read

S

Sam

Legend. Also the courtyard gate is sticking again.

14:09

P
Message Willow Court

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.

Next Door on a phone in dark mode: the main chat, one pinned message in a pill above the thread, a welcome from Deepak, and the composer at the foot of the screen
The Quick Request screen on a phone: Neighbor Requests and My Requests tabs over an empty state reading no requests yet, with a New Request button
The notifications panel open over the chat on a phone, with one announcement from Deepak, empty reminders and activity, and an event card showing behind it
The events screen on a phone with My Events selected, showing a Hiking Trip card with its photo, date, time, location, member count and a Go to Chat button

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.

Screen title32px · 600
Next Door
Section20px · 600
Neighbourhood events
Message15px · 400
Anyone free to sign for a parcel?
Meta12px · 400
Flat 4B · 2 min ago

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.

Chat
Events
Marketplace
Notifications
Members
Start and end
Where
Pinned
React
Read
Admin
Upcoming
Live now
Create
Event photo

Summer courtyard barbecue

Sat 14 June
18:30 to 21:00 (2h 30m)
Courtyard, by the bike racks
14 / 30 members

Created by Priya, Flat 4B

Join EventUpcoming · Hurry up
Event card state

The card is an invitation. The action is Join, and the rows say when, where and how full.

Listing photo

Borrow a drill for an hour

2h ago

Putting up a shelf this evening and mine has finally given up. Happy to return it the same night, and I will bring biscuits.

SSam · Flat 2A
3 helping
I can help
Market card state

Somebody else's request, not a listing. No price anywhere, and the action is I can help.

A tablet on a rust-coloured armchair in a dark room, running Next Door in dark mode with an event card open

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

Chat, events and a marketplace, on one member list.

Tables
30

Messages, reactions, reads, RSVPs, listings and their histories.

API routes
84

Every read and write goes through one, never straight to the client.

Components
54

Built once and reused across all three surfaces.

Commits
107

First to latest, 7 April to 11 October 2026.

Running cost
Free tier

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

Next Door poster: Tryyy the Guest Access, no signin required
Next Door poster: Create Your Own Community, get to github

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

  1. 01Run it in 1 real building, to see which half nobody needs.
  2. 02Make setting up a copy a few clicks, not a README.
  3. 03Add push notifications, so a parcel at the door reaches someone.
  4. 04Run a usability study, and close the 2 heuristics only partly met.

Guest access. No account, no email.

Try it

The demo is live with sample data in it, and the code for all of it is public. go ahead, let yourself in.

Great products happen when the right people meet.

Let's work together

If you are building something and want a designer who goes all the way in with you, my inbox is open.
LinkedIn