This is the companion piece to Acquired Taste, Episode 2. Watch the video above, or read on.
You are probably paying for at least three cloud storage services right now. Dropbox. Google Drive. iCloud. Maybe a couple of Google accounts you forgot about. Your files are spread across all of them in a way that made sense once and no longer does.
That’s where this episode started. We wanted to tear apart Dropbox the way we tore apart Slack last time, but the conversation quickly became about something bigger: the file metaphor itself is breaking down, and the products built on it haven’t figured out what comes next.
The Problem: Files Are Everywhere and It’s Getting Worse
The pain of scattered cloud storage isn’t new. But AI has made it significantly worse, and in an interesting way.
Before AI agents, the problem was inconvenient. You’d forget where you saved something, waste a few minutes hunting, find it, move on. The file still mattered as an object. You were going to read it, edit it, share it.
The shift happening now is that files increasingly matter as references. You don’t open them to read them. You need them to provide context for something else, usually an AI agent. A proposal isn’t a document you’re presenting; it’s context for the next version of the proposal. An old meeting note isn’t a record; it’s input for a new project brief.
When that’s the job, being scattered across four services in three different accounts starts to feel genuinely broken.
David put it well: the context in those files is only as useful as how accessible it is. If you’re pulling snippets out of old documents and pasting them into local project files so your agent has what it needs, that’s a sign the infrastructure isn’t doing its job anymore.
The File & Folder Metaphor Is Outdated
The file and folder metaphor has been with us since the early days of personal computing. It was a skeuomorphic design choice: make computers feel like physical desks, with files in folders, because that’s what people already understood.
We ported it to the cloud. We made it collaborative. We made it real-time. But we never actually got rid of the metaphor. And now it’s starting to show its age.
A library works when you’re the one going to find things. You need a system because you have to physically locate the item. But in a world where agents are doing the retrieval, the hierarchy doesn’t need to serve your mental model anymore. It needs to serve a machine’s.
The old question was: where did I put this? The new question is: can my agent access this when it needs it? Those require completely different answers, and the current tools weren’t built for the second one.
A Third Entity Just Showed Up
Dropbox was built for one-to-one: one person, one file. It evolved into many-to-one: multiple people collaborating around a single document in real time. That was a real breakthrough, and it changed how teams worked.
But there’s a third stage forming. Now it’s humans plus their agents, all working against shared files. Multiple people aren’t just collaborating on a document; their agents are pulling from it, writing to it, referencing it as context.
In that world, the file becomes less like a place where work happens and more like a consolidated decision record. The document exists not so anyone reads it cover to cover, but so the agents involved all agree on what’s in scope, what was decided, what the terms were.
The question of whether you have to organize it yourself stops mattering once agents can find and retrieve anything semantically. The question of whether it can be accessed by an agent that isn’t yours, on a different platform, with the right permissions, matters a lot.
David Built a Marie Kondo Agent
One of the first things David did when OpenAI launched was go to Dropbox looking for an AI-powered organization feature. Hoping there was a button. There wasn’t.
So he built his own. He called it Ms. Kondo. He created a knowledge base of rules and prompts so that when he had a new file, he could ask the agent where it should go, and it would place it in the right folder or create a new one.
It was clever. It also illustrated the exact problem. He was still thinking in terms of organization as the goal. The agent was helping him maintain a system that, in hindsight, might not be the system that needs to exist.
The smarter frame: you shouldn’t need to organize files at all. Not because you’re going to hand that work to an agent, but because the hierarchy might not matter if retrieval is semantic. You just tell the system what you need and it surfaces it. Location stops being meaningful.
What Dropbox Is Actually Doing: Dropbox Dash
At some point, Dropbox launched a product called Dropbox Dash. If you don’t know what it is, that’s kind of the point.
Dash is essentially a unified interface that lets you connect your other tools, like Notion, Google Drive, and Slack, so you can search and navigate across all of them from a single place. The idea is that Dropbox, because it already has your files, becomes the front door to your whole digital life.
This is a grab for the enterprise interface layer, and we think it misses the mark entirely.
Not because it’s a bad idea in the abstract, but because Dropbox isn’t the company to own that experience. They’re not Apple. They’re not Google, who at least has Gemini seeing your whole ecosystem already because you live in that ecosystem. Dropbox asking you to connect all your other tools is asking you to do the integration work for a UI play that they aren’t positioned to win.
The richer opportunity is much less glamorous and much more defensible: become the trusted context layer, not the front door.
What Dropbox Could Actually Be
Here’s the thing people actually like about Dropbox that they don’t like about Google Drive: it feels like your stuff.
Google, regardless of what the terms say, creates this lingering sense that they might be reading it, scanning it, using it somehow. Whether that’s true doesn’t matter. The feeling is there. Dropbox doesn’t have that problem. It feels like a private storage unit you rent on the internet, agnostic to platform, agnostic to device, nobody crawling through it.
That’s a real asset. And it’s exactly the kind of trust you’d want to lean on when the pitch is: let your AI agents store and access context here.
The version of Dropbox we’d pay more for: you upload anything, and it becomes machine-readable automatically. A video gets a transcript. An image gets annotated. A PDF gets chunked and indexed. Everything becomes flat, searchable, and agent-accessible. Not organized, just ready. The agents go in and get what they need. You don’t have to structure it for them.
And then you extend that outward. You’re not just storing files you made; you’re pulling in data from other SaaS tools you use. That data lives in Dropbox, accessible to any agent you authorize. Dropbox becomes the brain. Not the inbox, not the dashboard, not the front end. The brain.
The Front End Is Becoming Optional
There’s a broader shift this conversation kept circling back to.
Most SaaS software is, at its core, a database with a UI on top of it. The whole value proposition, for decades, has been: here’s a way to get data into a shared place and make it useful. The UI was necessary because people were the primary interface.
Now, agents are increasingly the primary interface. And agents don’t need the UI. They need the API, the MCP, the structured access. They don’t need to log in and navigate. They just need to call in and get the data.
That doesn’t mean UIs go away entirely. But it does mean that a large portion of the “product” many software companies have been building is going to get bypassed. The data layer becomes the product. The UI becomes optional for a growing class of workflows.
For Dropbox, that’s actually a strategic advantage, if they take it. They already operate closer to the data layer than most. They don’t need to pretend to be a productivity suite.
Markdown Is Having a Moment
A sidebar that kept coming up: markdown is the native format for this world, and most tools still resist it.
David pointed out that iA Writer, made by Information Architects, has been pushing markdown for years. Everything stored as plain text. No proprietary format, no lock-in, easy to translate into anything else. That always felt slightly idealistic. Right now it’s starting to feel prescient.
AI outputs well-structured markdown. Agents consume markdown. The entire ecosystem of LLM tooling is built around plain text and markdown. And yet Google Docs still defaults to rich text. TextEdit opens in RTF. Copy something out of an AI tool and paste it into a Word document and you spend the next ten minutes cleaning up formatting.
Dropbox Paper exists, and it’s a decent editor. But it could be a native markdown editor. And beyond editing, if Dropbox made markdown a first-class format across the whole product, and auto-converted uploads into machine-readable text, that would be genuinely differentiated.
The Agent Promoter Score
NPS, the Net Promoter Score, asks: would you recommend this product to a friend? The consumer era’s core metric.
What’s the equivalent for the agent era?
Which tool do your agents reach for when they have a choice? How much friction do they encounter when they try to use a given platform? How well does a product work as the context layer for agentic workflows, not just as a UI for humans?
That’s the metric shift happening right now. Products that have low agent friction and good API access are going to have an advantage that wasn’t measurable before. Products that built beautiful interfaces and neglected the data layer are going to start feeling that gap.
Agents need to be treated like users. They have needs, they have failure modes, they have preferences in the sense that some surfaces are easier to work with than others. Product designers are going to have to start designing for that audience, not just for the person sitting at the keyboard.
Is It Bad to Stop Organizing?
We spent a few minutes on whether outsourcing organization to AI creates some kind of cognitive atrophy. Whether people should still maintain the skill of knowing where their stuff is.
Honestly: probably not, for digital files.
We already generate more data than any person could meaningfully catalog. The cognitive load of keeping everything organized isn’t building some useful mental muscle. It’s just overhead. If a system handles retrieval well, the question of where things are stored shouldn’t have to live in your head.
The photo analogy felt right here. iPhone’s photo library auto-surfaces memories based on facial recognition, location, time. You don’t organize your photos. They’re just there, and the best ones show up when they’re relevant. Nobody wishes they had to manually tag and sort every image.
The filing-cabinet mentality served us when we had limited data and retrieval was manual. We’re past that. The organizational work was always a cost, not a feature. We just didn’t have an alternative.
Where This Leaves Dropbox
To be clear: we both still use Dropbox. We’re not calling for anything dramatic. It’s reliable, it works across platforms, and the trust thing is real.
But we do think they’re at a crossroads that they might not be handling the right way. Dash feels like a race for a prize that isn’t really theirs to win. The front-end AI interface is already dominated by Claude, ChatGPT, and the ecosystems built around them. Competing there requires either massive distribution advantages or a sticky enough workflow lock-in, and Dropbox has neither.
The thing they actually have, which is hard to replicate, is that storage layer trust, the agnostic, platform-neutral, private-feeling context vault, plus a long-standing relationship with people’s most important files.
Build infrastructure around that. Make it agent-native. Let other tools connect to it as the source of truth. Stop trying to be Apple.
If the head of product at Dropbox ends up watching this: we’ll pay more for what we’re describing. That’s the pitch.
About Us
Design Language is a newsletter for all product builders (PMs, Engineers, Founders, etc) who want to improve their design literacy, hone their sense of tase, and improve their craft when building products.
Jeremy Belcher is a 15 year product and design veteran. He has designed UX/UI for products used by tens of millions for brands like Google, Salesforce, Saturday Night Live, DirecTV, BMW, Emirates, Visa and in the past several years has focused on new enterprise workflow products. He runs the product studio Robot Heart, which designs, builds, and validates 0 → 1 B2B workflow tools for teams and founders.
David Issa is a digital strategy and product design leader with over 15 years of experience guiding companies through transformation. He has helped scale products and teams across healthcare, fintech, and enterprise software, translating complex systems into human-centered experiences. David runs a strategic design practice focused on aligning purpose, architecture, and execution—bridging design, AI, and organizational strategy to help teams build with clarity and intent.
