The Screen Is Already in Your Pocket

The wall screen families pay for expires the day the kids get phones, and the replacement is already in everyone's pocket, built to a standard that should be medical.

SUNDAY SHARE | BUILDING

Opinions are my own and do not represent my employer.

The question I keep getting is some version of the same one. You’re a doctor. Why are you building a family app?

The short answer is the one I give first, because it is true and it ends the conversation: my family needs it. Last month the school let out three hours early. The email landed in one inbox. The calendar invite landed in another. Nobody put it where both of us would see, so each of us assumed the other had it. Nash had a vet appointment the same afternoon. We run our household across a stack that does not talk to itself: shared calendars in iCloud Family, Things for lists, Reminders for the rest, and a group text where the detail that matters gets buried by dinner unless someone saves it. Scattered organization, four tools deep, each one supposedly the fix.

This is not a story about my disorganization. It is a story about a category. Every house with more than one calendar runs on the same broken stack, and the products built to fix it keep solving the wrong problem.

The Problem Isn’t Visibility. It’s Contribution.

Skylight figured out something real. Families will pay $150 for a screen, plus $99 a year, to hang the shared calendar on the kitchen wall. That demand is genuine. People want ambient presence: the family’s life visible without anyone having to ask.

The form factor is borrowed time. The wall screen works right up until the kids get iPhones. The moment that happens, the household’s center of gravity moves off the wall and into the devices in everyone’s hand. The appliance becomes decoration. You bought hardware with an expiration date set by your own kids’ developmental timeline.

The screen on the wall was never the real problem. The real problem is contribution friction. Watch how coordination apps die. A parent installs Cozi, sets it up, and nobody else ever touches it. Within a month a multi-player problem has a single-player tool, and the one person feeding it drifts back to the group text.

The problem was never that families cannot see the schedule. It is that only one person ever feeds it.

The Screen Already Exists

Here is the reframe. The ambient surface families want is already solved. It is the home screen.

Every person in the house is already carrying a glass panel they look at a few hundred times a day. The widget is the kitchen screen, distributed across every pocket, at zero marginal hardware cost. A product does not need to build a new surface. It needs to claim the one families already stare at.

That moves the whole thing onto one number. If adding to the family list takes one tap from the home screen, contribution stops being a chore and becomes a reflex. That is trust-in-ease: people commit to the system that asks the least of them, and the ones who never opened the app start feeding it without thinking.

This is a Builder move in a Legacy category. Cozi has fifteen million families. Life360 and TripIt have their own. All of them run dated interfaces, no real intelligence layer, and no way to credibly claim privacy, because their business models depend on the data they would have to stop collecting. That is not a feature gap a roadmap closes. It is the position they are stuck in. Builder vs Legacy is not a slogan here. It is a description of who can move and who cannot.

Why the Standard Matters

So back to the question. Why a doctor.

The differentiator was never that a physician built a family app. It is which standard came with him. I spend my professional life inside a field where protecting sensitive data is not a preference. It is the floor. You do not bolt privacy onto a medical system at the end. You build the system so the violation is not possible in the first place.

Port that standard into consumer software, where it almost never exists, and the architecture changes. Email parsing happens on the device, so the raw content never transits a server. Location is overwrite-only, so there is no movement history to leak or sell. No analytics SDKs, no ad networks, no third-party tracking. The test on every product decision is one question: would this be acceptable in a medical context? If the answer is no, it does not ship.

The pricing follows the same logic. The coordination layer is free forever. The intelligence layer is the paid gate. Data is free. Intelligence is paid.

That is the white space. Not another shared calendar. A family system where privacy is the structure and contribution is a single tap. Nobody large can build it, because building it would mean unbuilding their own business model.

Then the Platform Agreed

I planned this piece before WWDC. Then Apple rebuilt Apple Intelligence around the architecture I had been betting on.

The new system runs a coordinator that reasons over your personal context, pulls the right tools from your apps, and hands the language to a foundation model. The system decides. The model explains. Apple just shipped that split across every one of its platforms.

It drew my privacy line for me, out loud. Most AI providers keep your interactions by default and leave you to opt out. Apple named that and committed to on-device processing and private cloud compute, where your data is never stored or reachable by anyone. Privacy as structure, not a setting. The same standard, now the platform default.

App Intents turned the OS into the orchestration layer. A family app that adopts them lets a parent say “add soccer Thursday at four” and watch it land, no app to open. That drops contribution below a single tap. And the on-device model now ships free in the Swift API, so the intelligence that used to need a lab needs a download. AI stopped being something you invent. It became something you can afford.

V1 ships coordination first, the scattered stack pulled onto one surface, with just enough intelligence to feel magical. The base was never AI. The base is getting the whole family onto one screen. The heavier intelligence is the fast-follow, and as of June 8 the rails are real: iOS 27, Siri AI, on-device Apple Intelligence. The platform built the road the week I needed it.

One Bet Worth Naming

I will name what would sink it. The entire product rests on that one number. If contribution drops to a single tap and the people who never coordinate still do not participate, the thesis is wrong. I am staking the product on it in public, because a bet you cannot lose is not a bet. It is a brochure.

---

The early-release email still went to one inbox. Nash still made his appointment, barely. The short answer and the long answer are the same answer: the thing my family needs and the thing I am best positioned to build are one object, held to the standard I already carry. Porch goes to the wild this summer, for families and for groups of friends who want to run their life without surrendering it. The kitchen screen is not coming back. The next one is already in your pocket, finally with something worth keeping there.

— Adam

If this is the why, the how is its own piece: one physician, ten AI agents, a $360-a-year cost base, and what “shipped” actually means.