Here we will outline three architectural changes to how Anytype handles types, queries, collections, and tags. Previously, this was known as Lists 2.0 but we have renamed it to Collections 2.0 for now. Everything is currently just a proposal, nothing is set. The purpose of this post is to ask for co…

hey @kaye , First of all, thanks for the discussion around implementing this; I am hoping some of the feedback will be incorporated into the final product. After three weeks of ruminating on this, I think I finally fully understand the goal, and I do have some more practical questions that I hope m…

[image] sturdily: To be clear: Simple tag with no properties → just label, shows all objects with that tag Tag with properties → a label, shows all objects with that tag, and adds properties (what is maybe the of collections 2.0 multiple collections?) Tag with properties and template → a label…

Hey Kaye, [image] kaye: The distinction between a collection and smart collection isn’t much besides the query-ability to auto aggregate objects into the collection. I am still working through the new objects thread. And one idea is coming up while I’m reading, you’re writing about collectio…

[image] kaye: As for displaying the properties in the object header, this is something we have not fully figured out yet. Should there be tabs that all you to cycle through different collection properties of the same object? Should all properties from all collections be displayed? How about the …

I’d love to see a simpler and more user-friendly way to add new types in Anytype. Right now, every time I need to create a new data type, I tend to postpone it because the process feels too complex. Craft is a great example of how smooth this can be. It’s incredibly fast to create a new collection…

I don’t know Craft well enough. But based on the part shown in the GIF, it looks very similar: [anytype_capture] If you can, focus on the friction points in Anytype—the details that make a difference—and break them down step by step. That could help the team. In the process shown in this video, …

In the provided example, you’re extending an existing Page object. I’d like to create a new one. Currently, to achieve this, I need to create a new Object Type and then start adding such columns to the general Query Object View. This process is not intuitive. It would be easier to have some choic…

We have shared a prototype, please see this forum post: Collections 2.0 Prototype Hopefully this can make the discussions in this thread much more tangible about how the new system feels. I did not cover all topics in the prototype, but it’s should give a high level overview of how it functions. R…

This look sick! I really appreciate how much time and attention you put into thinking about how these sorts of mechanics work. I think the idea of an object potentially having multiple “types” matches the real world a lot better. Sorry I don’t have more helpful constructive feedback but just wanted …

Collections 2.0 Architecture—changing how we use types

News

ogokcocoball May 9, 2026, 8:13am 95

I felt the same way, so I shared my thoughts in a more recent post a few days ago.
What are your thoughts on the proposal I made there?