2 ms·
> Developers like to emphasize how they fund sustained future development of an app, but the reality is that when you cancel you usually lose access even to cur
by gnicholas 6y ago
> Developers like to emphasize how they fund sustained future development of an app, but the reality is that when you cancel you usually lose access even to current features (you arguably already helped pay for).
I make a browser plugin that functions as a productivity/accessibility tool. When I first started charging, I actually did grandfather in all our existing free users and give them perpetual access to the then-existing feature set. But it's not clear what it would mean to freeze people who had a paid subscription and then terminated it.
If someone pays for one month, do they forever get access to the version that they briefly paid for? How do I deal with customers who are upset that certain websites have changed and no longer work with old versions of our plugins? I would expect lots of questions from folks who want to know if this bug or that bug had been fixed by later releases (and then they would briefly subscribe to get perpetual access to the newer version).
Another commenter mentioned giving folks access to the version that existed a year before they stopped paying, but if I release version 1, then 2, then 3, someone might try out 3, stop paying, and then end up on 2. That seems confusing and suboptimal for everyone.
- maccard 6y agoThe jetbrains model only kicks in after a year. If you sub for 1 month, and cancel, you get nothing. If you sub for 12 months, you get a perpetual license for the version that was relesed 12 months before you finished.