An architectural philosophy asserting that individual files and folders on the filesystem should be the primary interface and permanent asset, with software apps serving merely as interchangeable tools.
The “File Over App” philosophy asserts that the documents you create are more important than the tools you use to create them. In this framework, durable files stored on your filesystem are the primary intellectual asset, while software applications are merely transient viewing and editing instruments.
For modern knowledge workers, software turnover is relentless. Note-taking tools like Evernote, Wunderlist, Springpad, and Roam Research rise, change their business models, or decline. When an application stores notes inside a proprietary database or cloud service, the user is held hostage: leaving requires painful export scripts, loss of formatting, and broken links.
The core axioms of File Over App
- Files outlive apps: A quality Markdown or plain text document can survive for decades, far outlasting the lifecycle of any specific venture-funded startup or software version.
- The filesystem is the operating system’s greatest feature: Hierarchical folders, metadata tags, hard links, and permissions are standard, universal capabilities provided directly by macOS and Unix.
- No lock-in by design: If an application becomes slow, expensive, or bloated, switching should be as simple as opening your existing folder in a different program.
- Composability: Multiple specialized tools can operate on the same folder simultaneously—for example, editing notes in Oyma, conducting batch searches in terminal with ripgrep, and pushing backups with Git.
File Over App vs App-Centric Silos
| Trait | App-Centric Silo (Notion, Evernote) | File Over App (Oyma, Obsidian) |
|---|---|---|
| Where data lives | Remote cloud database / proprietary blob | Standard directory on your Mac drive |
| Offline access | Limited cache; frequent data conflicts | Instant, full, permanent access |
| Migration effort | High friction (loss of embeds, properties) | Zero friction (already plain files) |
| Tool integration | Limited to vendor API integrations | Compatible with any CLI or desktop app |
How Oyma executes File Over App
Oyma was engineered around the File Over App principle from its first line of code. When you open a folder in Oyma, the application acts as an intelligent, responsive lens over your files:
- It never moves your notes into a hidden container or obscure library cache.
- Meeting recordings produce clean, standard Markdown records with YAML metadata and action item task lists.
- You can freely edit files outside Oyma using Terminal, Vim, or VS Code; Oyma detects file system events instantly and refreshes without re-indexing stalls.
Your files belong to you. Oyma is simply the fastest, most private way to write them and capture meetings on macOS.
Frequently asked questions about File Over App Architecture
Who popularized the File Over App philosophy?
The term was popularized by Steph Ango (CEO of Obsidian) in his 2023 essay "File over app," arguing that personal data should not be locked into transient applications that require recurring fees or server logins.
What happens to my data in a File Over App system if the app shuts down?
Nothing. Your files remain right where you saved them on your hard drive. You can immediately open them in VS Code, TextEdit, Neovim, Obsidian, or any other editor without converting or exporting.
How does Oyma embrace File Over App?
Oyma has no proprietary database schema or cloud vault. It is a lens through which you view and edit your standard Markdown files and into which meeting transcripts are saved directly.
Master file over app architecture with private Mac notes.
Store your thoughts in standard Markdown, transcribe calls on-device, and retain 100% data sovereignty.