How do you handle the friction of creating new Object Types? (Anytype vs. Tana workflow)

[kaye]

@360lime

Would it be possible to introduce a more dynamic, “on-the-fly” approach to Object Types? A system where we can quickly assign a loosely-defined type to a new object, and flesh out its rigid relations and templates later during our review process, without breaking the immediate flow of capturing data?

In short, the answer is yes. As @Shampra has mentioned, we have a big Collections 2.0 project underway which is upgrading the way that we use types. I can share some points as it relates to your post:

1. We agree that there is a lot of ‘front-loading’ on Anytype, whichmakes it a steep learning curve for many new users. A big reason for this is the object type system, which is a critical defining step to your organisation system. It is fantastic, but we wanted to find a way to reduce its complexity while maintaining its power. This is why we are dissolving the strict barriers of types to lower the ‘severity’ that comes with assigning types.
2. We agree that we want to minimise the gap between creation and organisation, and not have the latter get in the way of the former. In this new system, we are prototyping a sort of temporary base for new objects that are unassigned to any types/collections—you can imagine a kind of unsorted/inbox of some kind. This is similar to how the ‘Page’ type is used today as a defacto ‘base type’, but with some new UX improvements.

Feel free to take a look at the link I shared about how the new system will work and look forward to any feedback. Very happy to hear that you love Anytype.