What Survives When the Interface Dies

Yesterday, June 1, 2026, Strava shipped an MCP server. It opened a way to slice your own Strava data however you want, no developer skills needed, included with a subscription. In the same post, Strava restricted intermediary platforms, narrowed some third-party access paths, and made subscriptions required for Standard Tier API developers. One move says the interface in the middle matters less. The other says the data underneath it matters more than ever.

My cofounder and I had talked about this earlier this year. An app like Strava matters less as an interface once AI tools let you build your own views on its data, though the data itself still matters. The same pattern is showing up across software. The interface is being unbundled from everything underneath it, and the interface is the part that stops being the moat.

That unbundling seems to be happening in three waves, each removing a different layer: interpretation, then the app, then the OS. The question isn't whether apps disappear. It's which parts of them survive once the interface is no longer the default surface.

Wave 1: interpretation gets unbundled from the app

Most people already price this one in. The app captures the data, and a separate layer sits on top to interpret it: coaches, analytics dashboards, insight engines. AI commoditizes that layer. You don't need a third-party Strava coaching tool when an assistant can read your runs and tell you what they mean. Strava's own MCP is this wave, except the platform is reclaiming it. The company said developer applications were up 448% year-to-date and tied the surge partly to no-code AI tools generating apps that access its API. Third parties were already slicing Strava data this way, so Strava shipped an official version and narrowed the paths around it. The data capture survives. The interpretation business doesn't.

Wave 2: the app gets unbundled from the developer

This is "personal software," where you (or the AI) build the app instead of downloading someone else's. It runs along a spectrum.

At the simple end are consumer app builders for non-coders. Base44, which Wix bought for about $80 million in June 2025, is one clear case: describe what you want, and it handles deployment, hosting, storage, and auth. Its sweet spot is still simpler apps like workout planners, itinerary apps, budget trackers, and note tools, not deeply specialized backend systems. That's the long tail of the app store. Why download a generic timer or unit converter when you can generate the exact one you need?

At the serious end is prompt-to-app that ships real, deployable software: Lovable, Replit, Cursor, the Manus and Emergent crowd. Replit's agent plans, builds, and hosts an application without you leaving the browser. The constraint is no longer technical syntax, but knowing what you want built and saying it clearly. The question moves from how to build to what to build.

Wave 1 unbundles interpretation from the app. Wave 2 unbundles the app from its developers. The casualty is the single-purpose, long-tail app.

Wave 3: the app model gets unbundled from the OS

This is the most existential and the least built out, but the direction is clear. Nothing, the hardware company, is positioning Playground as a step toward an AI-native OS. Samsung is going further at scale, rebuilding One UI around system-level AI with Gemini at the center; at CES 2026 its co-CEO said it plans to double its Gemini-powered devices to 800 million this year, per Reuters. Apple is moving more cautiously: a Siri overhaul built on Google's Gemini, with on-screen awareness and the ability to act inside apps, running through Apple's own private-cloud infrastructure.

Push it far enough and the phone goes app-less. OpenAI is reportedly building an AI-agent phone where the assistant replaces apps entirely, targeting production around 2028. It reads your context and acts, instead of waiting for you to open something. Apps don't disappear; you just stop touching them. The assistant works across them, and the home-screen grid fades.

What survives

The same four categories survive all three waves.

Networks of people. You can't vibe-code your friends onto a leaderboard.

Proprietary data capture. An AI OS can't conjure Whoop's sensor data without Whoop.

Transactional and supply networks. You can't generate Uber's driver fleet from a prompt.

Trust and permissions. You can't prompt your way into regulated access, liability, identity, or institutional trust.

None of these is just a UI over data, which is why the three waves (commoditized interpretation, user-built utilities, and an app-less OS) leave them standing. What dies is the app as mandatory interface. What survives is the app as network, sensor, supply, or trusted permission layer.

How far along this is

Wave 2 still tops out at widgets and simple utilities for most people today, not full apps. Less technical builders stall when the backend, data model, permissions, or edge cases get complicated. Wave 3 is mostly keynote framing and early rollout. Samsung is rebuilding One UI, not shipping a separate OS, and Apple's Gemini-powered Siri is arriving in phases rather than all at once. App-less is a 2-5 year bet, not a 2026 reality. The interface is not worthless; good interfaces still compress judgment, taste, trust, and repeated workflows. The narrower claim is that the generic app screen is losing its monopoly as the place where software value lives.

How we're adjusting

We saw this in our own product. Users stopped caring about dashboards and wanted to plug their stack straight into our APIs to do the interpretation themselves. So we stopped treating the interface as the moat and are focusing on the things that don't unbundle as easily, like the data capture.

Strava read it the same way. Third parties were already building MCP-style experiences on its data, so Strava shipped its own paid version and tightened the access paths around it. Once you own the network, the sensor, the supply, or the trusted permission layer, you set the terms for anyone who wants to build on top. The interface is already being commoditized.