Shipping the Feature Nobody Demos

Nobody screenshots a deep link. You can't put it in a launch video. There's no "wow" moment on stage where a URL opens the right screen. And yet deep linking sat near the very top of our request board — third most-wanted, for a long time — because the people actually shipping apps knew something the demo never shows.

We added it in April 2025. It might be the least glamorous thing we shipped that year, and one of the most important.

What a deep link actually does

A deep link is the difference between an app that lives on the internet and an app that lives on an island.

Without it, every path into your app dumps the user on the home screen. Someone shares a specific listing? Home screen. A push notification says "your order shipped"? Home screen, go find it yourself. A campaign link promises one thing and opens another. Every one of those is a small betrayal of intent, and they add up to an app that feels disconnected from the world around it.

With deep linking, a link opens the exact screen — the specific record, the specific moment — inside the real native app. The share works. The notification lands somewhere. The campaign keeps its promise.

Table-stakes features are invisible when they work and glaring when they don't. That's precisely why they're worth building well.

Why the boring features earn their place

There's a pull, when you run engineering, toward the features that demo well. They're satisfying. They photograph. They make the roadmap look ambitious. But a roadmap made only of shiny things quietly rots underneath, because the unglamorous plumbing is what every shiny thing stands on.

Deep linking is plumbing. So is deep linking's cousins — the things that connect an app to sharing, to notifications, to the growth loops that let an app actually spread. None of it demos. All of it is load-bearing.

• Shiny features win the launch.
• Table-stakes features decide whether people can build a real business on you.
• The second list is the one that keeps them.

Listen to the request board

The other lesson is simpler, and I keep relearning it. The feature was near the top of the board for a reason. Our builders weren't asking for it because it was exciting; they were asking because they kept hitting the wall where their app couldn't connect to anything outside itself.

A request board is a map of where your tool stops being able to help. The loud, exciting requests are worth reading. But the persistent, unglamorous ones — the deep links of the world — are usually the truest signal you'll get about what's actually holding people back.

Ship those. Nobody will demo them. Everybody will need them.