Yes, absolutely valid concerns and I've though about those.
When cancelling the subscription, all existing notes and all data remains fully accessible (read and write). It’s a knowledge base, after all. Projects with more than 50 notes will not support adding new notes, but all other features remain fully functional.
About the idea of keeping the latest version without updates: interesting, but tricky to implement in the App Store. You'd need a feature switch for everything. OS compatibility updates would still need to go through or the app would not survive in the App Store (typically this is what would get users to upgrade for apps distributed outside of the App Store).
Even if the app were to disappear, you could still access your notes with a browser and copy the data over to another app. Not as convenient as using text files, but the ability to embed images into the notes led me to go with HTML.
When cancelling the subscription, all existing notes and all data remains fully accessible (read and write). It’s a knowledge base, after all. Projects with more than 50 notes will not support adding new notes, but all other features remain fully functional.
About the idea of keeping the latest version without updates: interesting, but tricky to implement in the App Store. You'd need a feature switch for everything. OS compatibility updates would still need to go through or the app would not survive in the App Store (typically this is what would get users to upgrade for apps distributed outside of the App Store).
Even if the app were to disappear, you could still access your notes with a browser and copy the data over to another app. Not as convenient as using text files, but the ability to embed images into the notes led me to go with HTML.
Happy to answer more questions!