Just to share some thoughts

[Naroc]

Roadmap Update: 2026 Feb

Here is the latest roadmap update, you can also view it here if you prefer a board view. As usual, what you see below is subject to change, however it’s the best outline we can provide of where our priorities currently stand. Here is the Town Hall 2026 Feb recording and Q&A. Moving forward, we will update the roadmap on a 2 month cadence, typically around the next Town Hall. Coming Up Next What we’re actively building and expect to deliver in the next two months. Core focus: Block-Based Re…

I appreciate the great updates released over the past two months. In particular, the wrap‑text feature in grid view has been incredibly helpful.

Thank you as well for sharing the detailed roadmap. Seeing so many promising features on the way has genuinely rekindled my passion for Anytype.

---

However, I do have some concerns about the prioritization of upcoming releases. In my opinion, Editor 2.0 and Properties should be the highest priority, as they are fundamental to how users work with Anytype.

No matter how many brilliant features Anytype introduces, it is ultimately a note‑ and document‑based application. That means several core concepts deserve focused attention:

1. Basic note‑taking workflows
   This is about how users interact with the editor while writing. People expect convenient ways to reorder lines, format text and blocks, highlight content, tag keywords, create links, and more.
2. The final presentation of a note/document
   This concerns how information is clearly structured and displayed. Users look for flexible formatting options such as lists, tables, annotations, and other creative block types.
3. The relational system for managing notes/documents
   This is about helping users organize information effectively. Anytype’s database‑like system aligns well with current PKM trends, but there are still missing property types and views—such as timeline view, rollups/relations, formulas, and rich‑text/bullet‑list properties. I would also like to suggest a checklist property with a progress bar, as it can flexibly support checklists, target lists, shopping lists, and sub‑tasks.

Properties are crucial because they handle information outside the document itself and are deeply connected to the strategic layer of personal or team knowledge management.

---

For all these reasons, I believe these areas represent the core values of a PKM system. They define the most essential part of the user experience—and they also strongly influence user engagement, long‑term retention, and ultimately the active user volume. These factors matter not only to users but also to developers, founders, and investors. They were also the areas where I felt Anytype fell short in the past few years.

Thanks!

[kaye]

Thanks for the feedback, Naroc. We absolutely agree. We would love to have an amazing Editor 2.0 today if we could. There are many challenges internally that we haven’t reconciled which is why we haven’t been able to start on it yet, but you can rest assured that we know this is a core part of Anytype and it needs to not only be improved…it needs to be fantastic.

In the meantime, we’re making quite a few upgrades to properties in Collections 2.0 if you haven’t seen. This will certainly have quite a big impact on the user experience of Anytype.

[Naroc]

@kaye

it needs to be fantastic.

That’s the best reason to explain why it’s late, and also the answer I expected to confirm. I have your word “Fantastic” – that is incredibly exciting! Thank you!

[kaye]

In the meantime, we are improving bugs and making it generally better—so hopefully that suffices for now. But with the Editor 2.0, we can make much bigger strides an unlock new features that are currently blocked by the old infrastructure.

[Naroc]

Absolutely! It’s great to know you already have features lined up that are just waiting for Editor 2.0 to unlock them. That really shows the depth of your vision.