Every product has a “yes” list. The features it shipped, the features it’s working on, the features in the changelog. The “no” list is harder to find. It’s the list of things you keep getting asked for and keep deciding against.
Ours, today:
- Real-time collaboration. The version history model is built for sequential edits; concurrent cursors would require rebuilding the storage layer. Maybe later, not now.
- Pixel-perfect Word export. We export to .docx with the structure intact. The exact margins, fonts, and footers don’t survive. They never do.
- A roadmap voting page. Voting makes the loudest users the loudest. We’d rather decide.
- Mobile apps. The web app works on mobile. A native app is a second codebase we can’t justify until paid usage is ten times what it is.
- Custom slash commands. The slash menu is the editor’s API surface. Letting users redefine it would break the muscle memory it’s there to build.
We’ll change our minds on some of these. The list will keep changing. The point is the list exists, in public, instead of “yes, eventually” being the answer to every feature request.