Ideas under the hood - Less interface, more content. Unobtrusive help - Quick start. You can write after launching the app: the quick note…

Ideas under the hood - Less interface, more content. Unobtrusive help - Quick start. You can write after launching the app: the quick note entity is activated, the cursor is cocked. Minimum actions before starting to type text: click the app icon - write - Simple navigation. For me this is a scroll from new to old. Like any dump, this is a natural and understandable way to find something visually - just scroll and search with your eyes. We often do this - Help for seamless keyboard work. It is often hard to remember yet another app's shortcuts, especially if they do not echo others, if they are unique, and if the app is not a work tool for earning a living. Functions important for blooming at full power hang in front of your eyes together with hints for their shortcuts - Intelligent grouping. I started researching a group of apps promising links between notes and discovered that promises turn into obligations. Notes need to be linked by hand! That is even more work. And I want less work. The service should be able to understand context and link notes into groups by itself. It can proactively gather note cards into stacks; if it makes a mistake somewhere, drag the card out with the cursor or into a suitable group. Visual and intuitive. - Contexts must be visible and available by click. Here they are in the lower-left corner of the screen - I also noticed that teams obsessed with the idea of showing links between notes, creating a knowledge graph, are enchanted by this idea and at the same time shift the work onto the user. But what is needed here is such a systematic approach to maintaining order. For example: I started taking notes with quotes and my reflections on books I read. And... nothing worked out. In the simple way - read, something resonated, write - I got another dump that needs to be sorted, tagged, and also needs thoughts from different books connected to each other. It is especially difficult when notes about different books are in different folders. Or another approach, where all thoughts from one book are in one note. After analyzing it, I understood that I should have prepared: create a space called "Books," somehow plan in advance there that I would keep notes from different sources. At least then building a knowledge graph would be easier. And the value of a knowledge graph is actually in finding non-obvious links, or obvious links encountered in different places. It should work by itself. The service should understand that there is a stack of notes with quotes, all of this is from books, which means relationships between them can be searched for and grouped. Or understand that these are repair advice notes and pull into this knowledge group the site of a manufacturer of beautiful chairs that I saved 12 years ago as inspiration - "Dude, their time has come!"