future Key applications are long-time commitments. They are an investment in time, and moving from one to the next app is usually non-trivial.
These kind of applications should not be chosen because of trivialities and what is currently popular. What application will still (possibly) be available several years from now? How hard is it to get my data out? Is it possible t trnsform my data to import it in anther application?
At the same time, an application must be pleasant to work with. If not, it will be an extra reason not to work.
Last, preferably application has the possibility to grow in use. An over-simplistic app wil probably make se reconsider when we start missing features.
Literature notes
HTSN - Introduction part I §1 - How to Take Smart Notes - Sönke Ahrens - literature notes Good methods give freedom to work flexibly - This book offers a workflow not just for one project, but for a broader solution, that gives flexibility and freedom
Fleeting notes
our important tools should be enjoyable, and open, so they can be used now and far in the future - What defines a good structure (or workflow)? - enough flexibility to change what you are doing while still being active within scope - This means there is not just one path, one thing to do - a wide ranch of actions all pointing in the same direction - possibility to choose what to do makes working so much easier - freedom to work on what we like - enjoyable work - The structure should be flexible enough, or big enough that it envelopes the big picture - this demands considering the big picture when planning - that means to look beyond the current project - note taking (as the current context) should be part of our bigger picture - zettelkasten as a life style not a quick solution - big picture → solutions that scale - our note taking / work environment should be workable for 10 or 100 times what we do now - that also implies time, does my solution work tomorrow? - open data / interoperable solutions only - Software agnostic