First Impression of the many things


Coming from Obsidian, there are a few major things I missed about Obsidian:

  • Everything can easily be keyboard accessed.
    • command+shift+up/down for highlighting multiple lines makes more sense to me (instead of moving lines upward or downward which seems to be more like command+control+up/down) → OR able to set our own hotkeys
    • Shift+enter for next line within relation block and enter to next object (like in general input)
  • Command Palette - where all actions can be used regardless of inputting locations or only relevant actions

Mouse access: Hidden sidebar always interrupt when I try to access the ‘…’ action or ‘+’ button → perhaps something like hot corner on Mac helps


  • I really like the illustration from the feature on Anytype website (“make your ideas stronger with each connection” section), where graph view can be fixed horizontally; tag, relation and type are shown in a clear manner. Because it provides a solid ground (not floaty) for exploring nearby relations. Perhaps this can be shown as display option or when exports
  • Hover preview only with command key or double click on Graph view (preview currently cover some objects)

Note Taking

I like how structure (with columns or inline relation block) can be formed with each object.

  • One thing I found cumbersome to do with structure is unable to turn multiple blocks (same level blocks) into single object
  • For example one process I go through is to (1) input notes on an article, then (2) organise / structure, then (3) see if it needs to be reference else where (turn into objects). Instead of: 1. input 2. make structure info object (move each item ∵ only one item will show, other will be missing) 3. turn into object for reference 4. put in the original article object
  • Grouping items into block might do, like nested block.
  • Batch convert to objects

I would like to have embed object or full view of object within another object (instead of preview) Maybe this could be more processing heavy though…
Forming hierarchy is what I do taking notes. Anytype does it quite well. I will stick with anytype for now.

Some other points or bugs

  • Sub-relation or sub-object would be helpful.
  • To be able to apply template manually, cause sometimes it is not prompted e.g. with changing object type
  • Support displaying svg file format
  • Unable to access object type or templates in search / everything
  • Impossible to have relation with number type as 0 (it becomes no value)
  • Unable to click object links with lock mode
  • User profile is not an discoverable object on search and system generated object (human) set
  • Not sure if it is necessary or if it will work, but sovereignty might increase with remote logout for other device?
  • Multi-window view overlap each other in the middle (I use macbook air m1) ∴ unable to view the whole pane side to side
  • No links are shown with attachments / media (e.g. pdf or audio file)

PS. Not sure if I will have time to check feature request or bug lists.


Hi @C.c what a great overview. For most of the points I totally agree with you and on many points we already have some work in progress. Also bugs added to the list for fixing.

Unable to click object links with lock mode

Could not reproduce. Can you share the video recording please or steps for reproducing?

  • command+shift+up/down for highlighting multiple lines makes more sense to me (instead of moving lines upward or downward which seems to be more like command+control+up/down) → OR able to set our own hotkeys
  • Sub-relation or sub-object would be helpful.

Can you please share the vision on how it should work and what are use cases for it

You can highlight multiple blocks with just shift up/down without any additional buttons needed


Point 1:
Sorry I didn’t state it clearly. I have no problem with highlight. The confusion was about moving block up and down with command+shift+up/down. In my mind, shift seems to be related to highlighting or selecting muitiple . So command+control+up/down for moving blocks make more sense. This is not a bug I encounter, but a conceptual thing that can be coped with.

Point 2: sub-object/relation
there are several plauslbe situation or levels in my vision:

  • Enable grouping in library. e.g. Resources → article, video, lecture; Position → CEO, manager

Sub-object type

  • Template for a object type can be treated as distinct object type
    • So every template accessible on object creation
    • This is a problem because set queries only allow one object type
  • Object creation with template can automatically create more objects from headings (not necessary for me)


  • Imagine creating information about a company, CEO is a relation (to show the word CEO in graph), then with every position, I will need to create another relation. The number of relation will accumulate and make it hardly to access on the relation panel. So to me, what makes it more meaningful and consistent across objects will be to have the input as the relation display, not the type or relation. Relation name can be “Position” (which doesn’t need to be seen in graph) then the demonstrated value or the actual (sub-)relation can be “CEO”.
    • Alternatively, the ability to create co-relation might help. On the company page, we can input position and person relating to each other (since it is on the same object page, relation to company can be assumed or not).
  • Doing conceptualisation and research, every concept (object) influences (acts as relations to) other objects. So the inputted object is the relation. While it doesn’t have to be in the relation position to demonstrate linking between two objects, these input would display relationships like “in the means of” or “via”.
    • Like the sample graph, the relation “inspired by” can be a simple relation, but it can also be an object explaining the inspiration points. If it is the current display in graph view, there will be an extra connection which doesn’t make sense for A is directly inspired by B and only once.
    • And most concepts belongs to a main concept/approach/area and the same concept name can mean different thing. Able to display core concept along with the sub-concept would be nice.
    • But then it might make sense to have the name of relations in bi-directional linking displaying on the two sides of the linking arrow (Rather than a long
  • As in value (relation) about the relation. e.g. Intensity for mood or positive/negative direction of certain factor. These relations don’t exist on their own.
    • This can be expressed with colours or connection force in graph view or an addition relation next to the existing relation in text mode.
    • Controllable connection force might be an interesting feature and would reveal a lot in graph view - less important objects can be further away from centre

My understanding in simple words (application can be complex though): Every relation is an object; every object can become relations. Relations are dynamic, interactive, and different across contexts.

Enjoy seeing anytype development.

PS. I just remember a design concept I like: for the app Flexcil, everything is within three click access. This makes everything quickly accessible.