Data & portability
Open file formats, an interoperable ecosystem, and self-hosting options ensure we have the power to manage our digital assets on our own terms.
What if this platform (or any platform) stops its service tomorrow? Or change their pricing? Or terminate our account for some reason? Or what if we found a better platform that we want to migrate? Even if they're well-funded, these questions have been bugging me for a long time now. I don't want to get stuck when a shutting down, transition or an acquisition happens.
I've been thinking about this for a long time. However, I had no clarity on how to address this concern. So, I started to save interesting takes on this subject.
Over time, I gathered valuable perspectives that helped me make connections and see patterns in this particular issue. However, the picture wasn't clear until I faced the problem.
-
Steph Ango
“File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read. Use tools that give you this freedom.
File over app is an appeal to tool makers: accept that all software is ephemeral, and give people ownership over their data.”
File over app (Jul 1, 2023) -
Andrej Karpathy
“TLDR: This is what software could be: private, secure, delightful, free of dark patterns, fully aligned with the user, where you retain full control and ownership of your data in simple, universal formats, and where tools can be extended and composed.”
Love letter to Obsidian (Feb 25, 2024) -
Dan Abramov
This might sound very hypothetical, but it's not. What I've described so far is the premise behind the AT protocol. It works in production at scale. Bluesky, Leaflet, Tangled, Semble, and Wisp are some of the new open social apps built this way.
It doesn't feel different to use those apps. But by lifting user data out of the apps, we force the same separation as we've had in personal computing: apps don't trap what you make with them. Someone can always make a new app for old data: Like before, app developers evolve their file formats. However, they can't gatekeep who reads and writes files in those formats. Which apps to use is up to you.
Together, everyone's folders form something like a distributed social filesystem.
A Social Filesystem (Jan 18, 2026) -
Jordan Singer
“Waiting for the day that design infrastructure companies are a thing. Think what Twilio's infrastructure enables developers to build as to what a theoretical design infrastructure company could enable for teams building design apps and tools. Wanna build the next Figma? Use [X design infrastructure company]'s infra and APIs.
We're all working on a 2D canvas with support for colors, styles, etc. Do we need to reinvent the wheel with every new tool?
Imagine a standard underlying design document representation that can easily be transported between the apps that live on X infrastructure. Design tools working more collaboratively together with each other instead of being private sandboxes.”
In a tweet (Jan 18, 2021)
I'll continue to add more thoughts and perspectives on this subject as I find them. Because I believe this is an important subject to be aware of and it's high time we start talking about it more.