3 ms·
I’m [very] interested. I saw your app before, but it was during my looking at so many different apps, I didn’t look too much into it. Being an HNer working on
by skinnymuch 6y ago
I’m [very] interested. I saw your app before, but it was during my looking at so many different apps, I didn’t look too much into it.
Being an HNer working on the product is a pretty big pro for me. Will be showing this specific comment to a few people for reference to Supernotes as well.
- fastball 6y agoGlad to hear it! Knowledge management is definitely a crowded space – probably because it's something that is almost universally useful to humanity if done "correctly". Being around HN for a while has definitely influenced how I think about the product and what I want to build. For a while I was wanting to build Supernotes as a federated service (and at some level I still want to do that), but for now the focus is mostly on making the most seamless UX.
- tmandry 6y agoYou seem to be hitting the nail on the head with regard to seamless UX. I’d gladly pay to support something like this, but the lock-in / “what happens if you go away” problem is real and holds me back from investing all my knowledge and time. Short of an actual federated system, a self hosted option OR just markdown export / backup of an entire database would completely alleviate that for me.
- fastball 6y agoSo we do currently have the ability to export all your cards as one giant markdown file. Obviously the issue with any sort of export with our system is that even if we export as markdown, the relationships don't really carry over into the export. But this is definitely something we are working to make as easy / thorough as possible. Data ownership by our users is very important, which we've spelled out in our terms[1] as well. [1] https://supernotes.app/terms/ https://supernotes.app/terms/