Hi Oliver,
many thanks for your interest in my app and for the kind words, it's much appreciated!
I understand that the lack of updates on the Keypoints website and forum may indicate to interested users that this project has been abandoned. But I can assure you that the app is still under continuous development.
That said, between regular work, family and other aspects of life, time available for development is still very much restricted. This is also the reason why I haven't updated the Keypoints website and forums: I don't want to generate more interest while it's not clear when I can deliver something. Also, given my time constraints, I currently want to focus on development.
I'd
love to work on this app full time and pour all my resources into it. But I also have to generate a sustainable income now and obviously have responsibilities towards my family (so taking a huge debt is no option for me). And the project's feature focus & target user group is likely too much of a niche to gather any serious funding. In addition, with this project, I also want to stay independent (I've seen too many projects die or change in negative ways after having been bought or funded). Unfortunately, it's a
common problem for indie software projects.
On the positive side, although much slower than I'd like, I
do make progress. I've also talked about the various aspects and features of my app in other forums, some examples:
Implemented:
- use filter elements (like keywords, labels, publications, files, etc) to define a search context, and display related (co-occurring) elements (
more info)
- search across relations: display all notes whose citing notes (aka "backlinks") or cited notes contain "..."
- filter notes by other notes, i.e. select some note(s) in the filter view to display all their cited notes
- self-contained plain text notes facilitate further processing with third-party applications (see
here and
here for some examples)
- parse each note into a data model of knowledge elements & relations, and expose this data in form of an API (
scripting API example)
- typed links: use
link types to describe the nature of a link relationship
Partly implemented:
- view (and ideally edit) multiple notes together, similar to Scrivener's "Scrivenings" mode (
more)
Planned (for later):
- all knowledge elements (notes, publications, authors, keywords, labels, link types, etc) should be fully featured plaintext notes (see e.g.
here and
here)
- offer custom attributes, and display these in columns that can be sorted & re-arranged (see
here)
Nonetheless, there's still some crucial functionality missing, there are a few crashing bugs (some caused by newer macOS system versions which I have trouble working around), there is a licensing issue to be resolved, etc. So I've still got some good amount of work to do before I can offer a public test version.