>
Tech News

The quiet app that ate my three favorite productivity tools

I had a rule about my dock. Every productivity tool on it had to do one thing better than anything else I had tried. That rule survived three app migrations, two platform switches, and one determined attempt to live without cloud subscriptions. It did not survive AFFiNE. After two weeks of daily use, the dock has four apps on it where it used to have seven, and one of those four is the local-first workspace that absorbed a writing tool, a whiteboard tool, and a personal notes app I had been running for years. Here is the story, with the parts nobody says out loud.

The dock rule that survived everything except AFFiNE

My dock rule was simple. If two apps on the dock could do the same thing, one of them had to go. The rule kept my setup honest for years. The block editor handled prose and shared wikis better than any alternative I had tested. The whiteboard tool handled visual brainstorming faster than anything on the market. The local notes app kept my files on disk as real markdown, which is the only reason I had not been bullied into a cloud subscription. Each one earned its slot. The dock was seven apps long and most of them were justified.

  • Dock rule: every productivity app has to do one thing better than anything else I had tried
  • Each of the three apps I closed earned its place for a specific reason
  • Local-first storage was the deal-breaker that kept me off cloud subscriptions
  • The dock was seven apps long and most of them earned their slots
  • AFFiNE is the first tool that absorbed three of them at once

The problem was not the apps. The problem was moving the same idea across three of them every morning.

What AFFiNE felt like the first time I opened it

The first thing the app showed me was Page mode, which behaves like any block editor you have used in the last five years. Headings, toggles, callouts, embeds. Familiar enough that I could write in it within minutes. The interesting part came when I clicked the toggle in the top right. The same view flipped into an infinite whiteboard, the kind you would normally open a separate app to see. Drag blocks onto the canvas, sketch arrows, link pages together. The toggle worked both ways and kept everything I had written intact. I have been waiting for a tool that did this for years, and the moment I saw it work, the dock rule was in trouble.

  • Page mode felt familiar within minutes for anyone used to a block editor
  • The toggle in the top right swaps Page mode for an infinite whiteboard
  • Blocks drag between the two modes without losing content
  • Pages can be linked to other pages in a way that survives the toggle
  • The dock rule was in trouble the moment I saw it work

The local-first moment that closed the deal

The single moment that changed my mind was not a feature. It was the folder on my disk. I downloaded the desktop build, created a workspace, and went looking for the file on disk. The folder was right there, full of readable files that I could back up, sync with Syncthing, or open in any text editor. Real files, on my machine, owned by me. That sounds like a small thing, and every cloud tool in the last decade has made me feel like it should not matter. It matters. Vendor lock-in falls away once your files are files again, and the moment I had that, the older app on my dock stopped opening.

  • The desktop install put a folder on my disk, full of real files
  • Real files meant I could back up, sync, and edit them with any tool
  • Vendor lock-in stopped being a question once the files were files again
  • The older local-notes app on my dock stopped opening after that
  • The moment was small and felt larger than any feature demo

Where the swap got harder than I expected

I want to be honest about the parts that did not transfer cleanly. The whiteboard features in AFFiNE handle the basics well. Solo thinking, one-on-one planning, quick dependency maps. They do not match the workshop features of the dedicated whiteboard tool I had been using. Collaborative sticky notes, voting, and template libraries are thinner, and a remote team that depends on those will notice the gap. The block editor is solid for prose and small-team wikis, but the template library and database features are years behind what you get from the big block editor incumbents. If your day leans on database views, formulas, or linkable record views, the new tool will feel underbaked.

  • The whiteboard basics work well, but workshop features are thinner than a dedicated tool
  • Collaborative sticky notes, voting, and templates are behind the dedicated incumbents
  • The block editor is solid for prose and small-team wikis
  • Template library and database features trail the big incumbents
  • If your day leans on database views, the new tool will feel underbaked

The two-week test on a real project

I did not want to base this on a vendor demo, so I moved one real project over. The project was a content planning document I had been bouncing between a writing tool and a whiteboard tool for months. I started in Page mode for the outline, flipped to whiteboard mode to map dependencies, dropped sticky notes for the parts that depended on other people, then went back to Page mode for the recap. I did not alt-tab once. The meeting was held in the same workspace the planning lived in, which is the kind of small win that does not show up in any feature comparison.

  • The content planning project migrated clean from two separate apps
  • The full flow happened in Page mode and whiteboard mode
  • I did not alt-tab during the meeting planning
  • The meeting recap was written in the same workspace the planning lived in
  • Two weeks of daily use found the limits better than any demo ever could

What I kept and what I gave up

The honest tally after two weeks. I kept the local-first storage, fast full-text search, and bidirectional links across modes. I gave up the dedicated whiteboard workshop features and a richer template library, neither of which I was using daily anyway. I gave up muscle memory from a tool I had been running for years, which is the real cost nobody warns you about. Switching out of a tool you have used for years means leaving muscle memory, templates, and integrations behind. The integrations were the bigger loss for me, because I had a few saved searches and one keyboard shortcut I had wired up. None of those were dealbreakers, but they were noticeable.

  • I kept local-first storage, fast full-text search, and bidirectional links
  • I gave up dedicated whiteboard workshop features and a richer template library
  • I gave up muscle memory from a tool I had been running for years
  • I gave up a few saved searches and one custom keyboard shortcut
  • The cost nobody warns you about is muscle memory, not features

The trade-off I would tell a friend about

If your pain is owning your notes and searching them forever, AFFiNE is the cleanest answer I have found in years. If your pain is heavy real-time co-editing with a remote team, the new tool is a step behind the tools you are using now. If your pain is deep workshop features in a whiteboard, the dedicated tool still wins on workshop depth. If your pain is database views and formulas in a block editor, the big incumbents still win there. AFFiNE wins where seamlessness between writing and visual thinking matters more than any single feature being the deepest version of itself. That is the trade-off worth knowing going in.

  • Owning your notes and searching them forever, AFFiNE wins
  • Heavy real-time co-editing with a remote team, the dedicated tools win
  • Deep workshop features in a whiteboard, the dedicated tools win
  • Database views and formulas in a block editor, the incumbents win
  • Seamlessness between writing and visual thinking, AFFiNE wins

Bottom line

AFFiNE is not perfect, and pretending otherwise is not useful. The workspace app is good in ways that matter and weak in ways you should know before migrating. The honest path is to move one real project over, time yourself against the seam-removal overhead you are paying today, and decide from there. Migrating everything on day one is the fastest way to give up on any new tool. Give it two weeks on a single project, see if the seams between your apps actually shrink, and decide from there. If the seams shrink, you have just saved yourself a small part of every morning.

Leave a comment