You write into an app. The app saves your work. You close the laptop. Where, exactly, are your words right now? For most writing tools, the honest answer is: in a database you don't control, in a format you can't read, on a server you don't own. This isn't a technical accident. It's a business model called vendor lock-in, recognized as a design pattern for at least three decades. And once you understand how it works, you'll never look at "your" writing in someone else's app the same way again.
You signed up for the writing app two years ago. You've written half a book in it. Hundreds of pages, organized into chapters and sub-pages and nested folders. The app has been your second brain.
Today, for some reason — maybe price, maybe principle, maybe a feature gone wrong — you decide to leave. You go to export your work. You get a zip file. Inside the zip file: a tangle of nested folders, files with cryptic auto-generated names, broken internal links, missing images, lost formatting. Two years of careful organization, returned to you as rubble.
You spend a week trying to piece it back together. Some of it can't be salvaged. The structure is gone. The cross-references are dead. You make a decision you didn't want to make: it's easier to stay than to leave. This is the moment the business model worked.
Most writing apps store your work in proprietary databases you don't control. Vendor lock-in is a recognized design pattern — the cost of leaving is made high enough that staying becomes the default. Real data ownership means your work was always yours, in a format you can read without the app.
What's actually happening?
Most productivity software stores your work in a proprietary database. The database is optimized for the app's internal features — collaborative editing, search, complex permissions — and it represents your work in a format only the app can read fluently.
When you ask to export, the app converts the proprietary format into something portable. The conversion is lossy. Some structures don't translate. Some links break. Some metadata vanishes. The portable version of your work is a fuzzy photograph of what you actually wrote.
There's a name for this in the software industry. It's called vendor lock-in, and it's been a recognized design pattern for at least three decades. The Berkman Klein Center at Harvard has published research on it. The mechanism is simple: the cost of leaving is made high enough that staying becomes the default choice. The proprietary format is the moat. The lock-in is the revenue model.
A more recent term, coined by the writer Cory Doctorow in 2022, is enshittification. Doctorow described a predictable life cycle of digital platforms — they start by being good to users, then extract value from those users, then degrade in service of the bottom line. Lock-in is the precondition that makes enshittification possible. Without lock-in, users would leave at the first sign of degradation. With lock-in, they stay.
Why isn't "we offer export" enough?
The standard response from software companies, when asked about data portability, is "we offer export." This is technically true and substantively misleading.
Export-as-an-event is not the same as data ownership. Real ownership means your work lives in a format you can read with any tool, on a storage system you control, without going through an export process at all. The work was always portable. The work was always yours. There's no migration to perform, because the work never moved.
Most writing apps don't offer this because they can't. The business model depends on the database. If your work lives in plain files in your own storage, the app loses its lock-in. The app becomes a tool you use rather than a service that owns you.
The few apps that do this differently are easy to spot. They tend to use plain text formats like Markdown. They tend to store your work in a location you control — your own Drive, your own Dropbox, your own folder. They tend to be priced as software rather than as a hostage situation.
What actually helps?
The principle is simple: your writing should live somewhere you control, in a format you can read without the app.
In practical terms, this means choosing tools that store your work as plain files, not in a proprietary database. That use open formats — Markdown is the de facto standard for prose — that any text editor can read. That save to a location you own. That don't require export, because the work never had to be imported in the first place. That treat lock-in as a flaw rather than a feature.
There's also a useful psychological frame here. The American psychologists Edward Deci and Richard Ryan, working since the 1970s, developed self-determination theory — a framework for understanding human motivation. One of their central claims is that autonomy is a basic psychological need. People function better, and feel better, when they have meaningful control over the conditions of their work. Being trapped in a tool, even a good tool, exacts a quiet psychological cost. The autonomy you don't have is a tax you pay without seeing the line item.
How Wretify approaches this
Every word you write in Wretify is saved instantly to your own Google Drive, as a plain Markdown file. There's no database. There's no proprietary format. There's nothing to export, because the files are already yours.
If you open your Drive right now, after writing in Wretify for a week, you'll see folders like Books/Quiet Hours/Chapter 1.md. You can open those files in any text editor. You can move them anywhere. You can copy them. You can read them in fifty years on a computer that hasn't been invented yet, because Markdown is a plain text format and plain text outlives every other format we know of.
If you decide to leave Wretify, there's nothing to do. Your writing is already in your Drive, already in a format every text editor can read. The escape door is always open, because there was never a cage.
I built it this way because I'd had four years of work trapped in Notion when I tried to leave. The zip file was rubble. I spent weeks trying to reconstruct what should have been mine all along. I didn't want anyone else to have that experience with my software.
I also built a tool inside Wretify called Liberation — a Notion importer that doesn't just copy files but reconstructs the structure, heals the broken links, and reorganizes the content into clean Markdown. It's free, with no limits. It's a small adversarial move against the dominant business model of the category. I think more software should make adversarial moves like this.
The escape door is always open, because there was never a cage.
- Most writing apps store your work in proprietary databases, not in files you control.
- Vendor lock-in is a recognized design pattern — the cost of leaving is made high enough that staying becomes default.
- Cory Doctorow (2022): enshittification is the predictable life cycle of platforms. Lock-in is the precondition.
- Self-determination theory (Deci & Ryan): autonomy is a basic psychological need, including in how you work.
- "We offer export" is not the same as data ownership. Real ownership means the files were always yours.
- Wretify saves every word to your own Google Drive as plain Markdown — no database, no proprietary format, no cage.
This article was written in Wretify. Try it free →
Frequently asked questions
Because today's good app is tomorrow's acquired-and-degraded app. The history of consumer software is full of tools that were once excellent and are now compromised. Lock-in is the mechanism that traps you when that happens.
Markdown is simpler than Word or proprietary formats, intentionally. It handles prose, headings, lists, emphasis, and links — which is most of what nonfiction writing needs. What it doesn't have is the brittle complexity of richer formats. That simplicity is why Markdown files written today will still open in fifty years.
If your work is in a proprietary database, you have a serious problem. If your work is in plain Markdown files in your own Drive, you have no problem at all — the files are still yours, still readable, still organized. The app's fate doesn't affect your work.
Because the business model is harder. Without lock-in, the app has to win on quality every month. That's a more honest contract with users, and a more demanding one for the company.
A milder one. Google Drive is open enough that you can sync your files to your computer, back them up to other services, or migrate to alternatives like Dropbox or iCloud Drive without losing the underlying files. The Markdown files are yours regardless of where they're stored.