Invisible Interfaces

The most interesting products I’ve fallen in love with this year don’t really have an interface.

You don’t need to open another app, go through another onboarding, or find another dashboard. You simply reach it the way you’d reach a friend, through a text thread or a phone call, and on the other side sits an agent that is connected to all the tools you use every day, such as your email, your calendar, your messages, your accounts. Then you can simply tell it what you need and it goes off and does it for you. Replies drafted, trips arranged, subscriptions cancelled, appointments moved. The apps it operates are all still there, humming underneath, but you just never see them anymore. They disappeared.

Watching this happen has clarified something I’ve been thinking about for a while. We are witnessing a new step being inserted in front of every interface we’ve ever designed. In the last years, using software meant going to the software, opening the app, learning its layout, and navigating its particular logic. Now you increasingly interact with one interface that is connected to all the other interfaces, and the moment that layer works well enough, the interfaces behind it begin to fade from view. They don’t fade because they got worse, but because nobody is looking at them anymore.

That is what an invisible interface actually means to me, and it has nothing to do with minimalism or fewer buttons. It means that the interface of the product you built, the thing your team obsessed over and tested and polished for years, basically becomes a back-end, and its primary user is no longer a person but an agent acting on a person’s behalf.

When your user becomes an agent

I would encourage every designer to sit with that thought for a moment, because it is genuinely destabilizing. The craft I grew up in assumed a human on the other side of the glass, and every decision we made about hierarchy, contrast, motion, or copy existed to help that person see, understand, and act. When the entity clicking through your product is an agent, most of that craft becomes invisible to the one doing the clicking, and your beautiful checkout flow gets traversed in two hundred milliseconds by something that has no appreciation for your easing curves.

This doesn’t mean design is no longer relevant, but it does mean it is migrating to another level. The interface layer of an individual service is turning into something closer to a protocol, which needs to be legible, structured, operable, and honest about its state. Designing for machines is still design, just in a different form. The human-facing craft, the part of our work that earns love and loyalty, moves up a level to wherever the person actually is, and increasingly the person is sitting in one conversation that touches everything.

What this means if you’re building

If I were starting a product today, this would change my thinking from the very first prototype. I would stop imagining my product as an app, as a destination trapped in a fixed screen on someone’s home screen, and start imagining it as a service that needs to live everywhere its users live. It would need a presence on the laptop, on the phone, on the TV in the living room, inside a conversation with an assistant, and one layer beneath a voice in someone’s ear. The app becomes just one of many forms the service can take, and quite possibly not the most important one.

There is an uncomfortable truth in this for anyone who believes great UX alone will save them. You can build the best product interface in the world and still lose if the layer where your users actually live cannot reach you. In a world where a new step sits in front of every app, being connectable becomes as existential as being usable. Distribution stops being about winning a spot on the home screen and starts being about being trusted, integrated, and preferred by the interface above you. The best end-to-end experience beats the best interface, and the speed from intention to outcome matters more than the beauty of the journey, because increasingly nobody witnesses the journey at all.

Interaction itself is widening too. We built an entire discipline around explicit input, around taps and clicks and keystrokes, but the layer in front doesn’t sit around waiting for input. It reads context, anticipates what you need, acts proactively, and checks in when it should. The products winning attention right now are not winning because of a smarter model underneath. They are winning on the harness built around that model, on the integrations, the permissions, the memory, the persistence, and the willingness to keep going until a task is actually finished. That harness is a design artifact, which means somebody shaped it, and that somebody should be us.

Trust, when there’s nothing to look at

This brings me to the part I find most exciting, and the place where I believe the real design work of the next decade lives.

So much of what we called good interface design was secretly trust design. The confirmation screen, the progress bar, the padlock in the address bar, and the receipt landing in your inbox were all ways for an interface to tell you that it heard you, that it was doing the thing, and that here was your proof. Trust was built visually because the visual layer was all we had.

Take the interface away and those old signals evaporate, while the stakes explode at the same time, because this new layer reads your mail, spends your money, and speaks in your name. It is no accident that the loudest conversation around every product in this new category is about trust, about what it can access, what it stores, and what it might do when you are not watching. The biggest design problem in this category is no longer usability. It is legitimacy.

So how do you design for trust when there is no interface to carry it? I believe it lives in three places. It lives in how the agent communicates, in its tone, its honesty, and its restraint, in whether it admits what it doesn’t know and asks before it assumes, because every sentence is now a design decision and the conversation itself becomes the brand. It lives in how you show what is happening on the other side, not through a wall of logs but through a considered kind of transparency, the reassuring feeling that the machine’s work is visible whenever you care to look. And it lives in the approval moment, that brief flash where an interface does appear right before an action is taken, carrying exactly enough context for a confident yes or no. As the interface shrinks, that moment becomes one of the highest-craft surfaces in all of software, because the fewer pixels that remain, the more each one weighs.

Design isn’t disappearing along with the interface. It is concentrating, and all the care we used to spread across hundreds of screens now pours into a handful of moments, into a sentence, a summary, a request for permission. Those moments will decide which services people let into their lives and which ones they quietly disconnect.

The designer’s job just got bigger

All of this leads me to a conviction that has only grown stronger as the interface has grown quieter: the role of the designer is not shrinking, it is expanding into everything the interface used to hide.

If the interface is no longer the product, then the screen is no longer the canvas. The canvas becomes the entire end-to-end experience, and shaping it becomes our job in the fullest sense. It is now a design decision where a product lives, how it enters someone’s life, how it behaves in a chat thread, on a phone, on the TV in the living room, or as a voice in the kitchen, and how all of those moments feel unmistakably like they belong to the same service. Every touchpoint a product has with a customer, in whatever context it appears, is something a designer needs to consciously shape, because if we don’t, it will simply be shaped by default.

And this is where brand stops being a layer and becomes the structure itself. Brand used to be something applied to a product, the coat of paint on top of the interface. When the interface dissolves and a service shows up in a dozen different environments wearing a dozen different forms, brand becomes the connective tissue that holds the experience together. It is the character a customer recognizes when there is no logo on screen to recognize, carried in the tone of a sentence, the restraint of a notification, the confidence of an approval request, the feeling that this thing knows you and behaves consistently no matter where you meet it. In a world of invisible interfaces, brand is what remains visible, and building it is design work of the highest order.

The step before

Some will read all of this as the quiet disappearance of our craft, and I believe the exact opposite is true. What is disappearing is the overhead, the navigating and managing and the administrative distance between wanting something and having it. What remains, and what grows, is the essence: intention, outcome, and the quality of the relationship in between. That relationship has become a design material, and together with the brand that carries it, it might be the richest one we have ever been handed.

The best interface of the coming years might be one you never see, and designing it, designing the invisible, is the most interesting challenge on the table. I can’t think of a better time to be a designer.

LFG.