Flo State

Flo State is a minimalist Markdown editor for macOS that puts speed, local files, and focused writing ahead of a large workspace platform. It opens a folder of notes, treats every note as an ordinary .md file, and gives that collection a clean native interface. There isn't a proprietary database sitting between the writer and the work. Other editors, scripts, version control tools, and file sync services can keep reading the same files, which makes the app appealing to people who want a pleasant editor without committing their notes to another closed system.

The app is written in Swift and uses a native Mac editing experience rather than wrapping a web editor in Electron. Flo State says it launches in about a tenth of a second, uses roughly 50 MB of memory after launch, and sits at 0.0 percent CPU while idle with a note open. Those numbers describe its central design choice. The editor should stay out of the way, appear quickly when an idea arrives, and avoid consuming a noticeable share of the machine while it waits. That posture matters most for people who leave their notes open all day and don't need a browser-scale application just to edit text.

Writing happens in a live Markdown view. Syntax remains editable, while common structures can appear in a more readable form as the document settles. Typewriter mode keeps the current line at a steady height on screen, heading folding collapses sections in longer documents, and clickable checklists support task-oriented notes. Wiki links connect notes with double brackets and provide autocomplete, including support for aliases, heading links, and embedded images. Pinned notes keep frequently used material near the top of the sidebar, and keyboard shortcuts cover formatting, headings, lists, folding, tabs, and search.

Flo State also handles richer technical notation without turning the source into a custom document format. GitHub-flavored Markdown tables render as aligned tables. Fenced Mermaid blocks become flowcharts or sequence diagrams, while inline and block LaTeX render through KaTeX. Images can be pasted or dropped into a note, then the app saves them in an attachments folder beside the notebook and displays them inline. These features make it useful for technical journals, architecture notes, research, and project documentation where plain prose isn't enough but portable source files still matter.

It fits Mac users who already think of a notebook as a folder rather than an online account. Someone with an existing Obsidian vault can open the same folder in Flo State because wiki links, image embeds, and front matter are supported. Someone starting fresh can place a notebook in any chosen location, including iCloud Drive, and use the normal file system around it. A shortcut opens the daily note and adds a dated title when that note doesn't exist, which supports lightweight journaling without introducing a separate calendar system. Light and dark themes can be adjusted with background, text, heading, accent, font, and contrast choices. That gives the interface some flexibility without making visual configuration the main event. It also keeps the same notebook understandable outside the app, whether a user searches it from Finder, processes it with a script, reviews changes in Git, or opens an individual file in another text editor.

The clearest distinction is how little infrastructure Flo State asks the writer to accept. Notes stay on disk, there is no account requirement described on the product page, and the app doesn't operate its own synchronization service. If cross-device sync matters, the folder can live in iCloud Drive, Dropbox, or a Git repository and move the same way other files do. That keeps ownership simple, but it also means the user is responsible for choosing and managing sync and backups. The app is deliberately Mac-only, with support starting at macOS 14, and the product page says there are no plans for Linux or Windows versions.

Flo State is free and open source under the GPL 3.0 license. The source code is available on GitHub, so developers can inspect it, build it, contribute changes, or follow the project as it evolves. There isn't a paid tier or bundled cloud service to evaluate. The practical decision is whether its focused native experience and portable file model cover enough of a writer's workflow. For Mac users who value quick launch times, low idle overhead, live Markdown rendering, and direct control of their files, it's a thoughtfully narrow option. Teams needing browser collaboration, managed sync, or broad platform support will need to supply those pieces elsewhere.