Every app ships the same UI to a power user and someone who signed up 30 seconds ago. It's 2026. We can do better than that. Software should reshape itself around whoever's using it. Point your repo at @getdiffer and see the version each of your users should get.

The next Adaptive Software Demo Night is coming up on Thu, Aug 20. Register: luma.com/2w5gj3ky @CloudflareDev @getdiffer @carlagriffs

We built our own chat app for internal use. Nothing fancy. Then we deployed it on @getdiffer It stopped being one app. The screenshots below are the same product, on the same day, used by different people on our team: → The first is the default view. Our design engineer Ion, who built this chat, wanted something calm and minimal that doesn't distract from actual work. → Noam preferred a bento layout. Everything that needs his attention at a glance, without navigating between channels. → Jules wanted notifications to be harder to miss. Channel alerts are more prominent and show message previews. Nobody filed a feature request. Nobody shipped a build. Each person asked for what they wanted while they were using it, and got it, on their version only. These adaptations are visible, and layout is the easiest thing to put in a screenshot. But they're not the only kind. The channel you open first every morning quietly moving to the top, without you ever favoriting it. Link previews staying collapsed because you never click them. You always jump to latest; your colleague always reads from where they left off. The agent observes and adapts. These are adaptations nobody would screenshot, because nobody would notice them. You'd just notice the software stopped getting in your way. Importantly, there are also limits. I have a slight preference for threads. My colleagues wanted quoted replies. How a message relates to another message is shared state and that does not adapt. If my version threaded and theirs didn't, we'd be reading different conversations. Adaptation stops where the shared model begins. We've drawn other boundaries deliberately: everyone's version renders from the same design system, no matter how it's arranged. That's a developer choice, not a user one. And the developer can still ship. New features go out to everyone, across every version. Static software has to pick an average user and build for them. Adaptive software doesn't have to. This is a few days old. Curious what it looks like in a month.

We ship one version of software to everyone. Not because it's better, because per-user used to be impossible and unaffordable. That constraint is disappearing. Coding agents can give anyone their best version. New talk on what breaks, what it unlocks, and the hard parts we're building through. "The Pipeline is Dead" 👇 youtube.com/watch?v=bRnoEpoK…