The Death of the App: Designing for Conversation
How Meta’s Muse moves away from buttons and towards relationships
The era of clicking through menus is ending. For decades, software design has been a series of commands: click this, drag that, select from a dropdown. It is a transactional relationship. But as artificial intelligence moves from a novelty to a utility, the interface is shifting from a dashboard to a dialogue. Meta’s Muse is a primary example of this transition. Instead of building a complex suite of features, the designers focused on a single, persistent relationship. The goal was not to build an 'AI app' but to build something that feels like messaging. This is a fundamental shift in how we interact with machines. We are moving from being operators of tools to being participants in conversations.
The Three Layers of Understanding
One of the hardest problems in AI design is the spectrum of user expertise. A casual user wants a simple answer; a power user wants to see the logic. Muse solves this through progressive disclosure. It offers three distinct levels of interaction. At the top, there is a simple emoji that communicates the agent's status. Below that, a task list provides more detail for those who want to know what is happening. At the deepest level, there are raw logs for engineers. This prevents the interface from becoming cluttered for the average person while ensuring the technical user is never left in the dark. It is a way to manage complexity without making it visible to everyone.
AI agents should be designed for conversations with people, not interactions with software.
This approach extends to how the agent handles data. Most software requires you to input information manually. Muse, however, can ingest existing digital lives. Alex Cornell, the design director, demonstrated how the agent could take years of saved Instagram posts and transform them into a structured shopping catalog. It turns forgotten data into immediate utility. This isn't just about convenience; it is about the agent becoming a continuous extension of the user's own memory and preferences. The machine isn't just responding to prompts; it is anticipating needs based on a long-term context that a standard app could never maintain.
- Prioritise persistent relationships over isolated threads
- Use progressive disclosure to manage technical complexity
- Treat personal data as a continuous context, not a one-off input
- Design for conversation, not command execution
There is also a psychological dimension to this design. When an agent works, it shouldn't feel like it is 'calculating'. Many products show 'thinking' steps as a way to hide latency, but Muse aims for speed that allows the agent to work quietly. The interaction is meant to be seamless. Even the way users communicate with the agent matters. Cornell noted that polite, specific prompting often yields better results than frustration. We are, in effect, learning how to manage a new kind of social entity that exists entirely within our screens.
Ultimately, the success of these agents will not be measured by how many features they have, but by how much they disappear into the background of our lives. If the interface is perfect, you don't notice it. You only notice the person—or the intelligence—on the other side of the chat. The transition from software to agent is the transition from tool to companion.
The future of software is not a better menu, but a better conversation.