What would be your use case and is there something in particular that leaves you undecided between Joplin and StandardNotes?
You are not Adobe or Autodesk to pull off a subscription model. Not successfully.
Sell a perpetual license that is valid for the current version plus anything that is released in X months after that.
Then, sell an option to extend the access to upgrades for Y% of the original purchase price once X months are almost over. If X months are over, sell the same option with a mark-up.
This is universally perceived as a fair arrangement and it gives you a recurrent revenue from people who do keep on using your software (just like with the subscription). Best of both worlds.
I'd gladly pay for the software and repurchase at major releases (if I wanted to upgrade)! I'm not looking for more subscriptions though. Give it a thought. I'd like to be one of the paying customers :-)
The application is sold as, "with data longevity in mind", but the subscription model makes me feel like that is only the case while I pay for a subscription. From what I read in some of your other comments, that may not be the case, but it's still a worry. What if I can't access my notes/data in the future unless I have an active subscription?
A must have for me is a code-block (three backticks enter or similar).
A killer feature would be a rest api so I could integrate with cli tools (bash, jq, grep, etc) without having to parse html.
I’m excited to try this out.