Tags as Nested Collections
As shared in the recent Town Hall, I added a short clip to the first post on how tags could be adapted with nested collections in the new system. As mentioned, you can use tags as a property (like today) in Collections 2.0 without the need to change anything. However, I believe for those who would like more organisational power with their tags, using nested collections (and hiding collections display) would be an alternative approach.
Breadcrumbs & Flow
I agree with both of you, @Shampra and @Code-Jack. Improving the navigation between linked objects would be hugely beneficial to all users of Anytype, especially to those who are coming from apps with tree hierarchy structures and breadcrumbs (99% of people). At the same time, it’s actually incredibly difficult to do well because there is no inherent start or end point to the navigation—which is difficult to create convenient UI for. While it’s unlikely that an object-based navigation system would ever as convenient/simple as folder trees and breadcrumbs, I do think there is notable room for improvement.
One idea I had was to allow users to define ‘priority links’ between objects. When there are priority links set on an object, the system can render a faux breadcrumb structure on the UI that makes it easier for the user to navigate. There are many issues with this though. One, it’s cumbersome. Two, it requires manual setup. Three, it’d only be used by power users. Four, it’d not scale naturally in a space with evolving complexity (since it’s manual).
Another idea is that nested collections could simulate this type of navigation. What’s problematic is whether or not it makes sense to enable branches and infinite depth for nested collections. This could create all sorts of other issues.
All that being said, we could try to simply improve the UX and ease of use of the current flow implementation and not rework the underlying structure. That’s an easy win. Alas, too many ideas, too many bugs, and too little time. 