3 ms·
Personally, I'm fine with all of those, with caveats in (4) and (5). Products should be fit for purpose, and therefore problematic bugs (particularly security r
by icebraining 9y ago
Personally, I'm fine with all of those, with caveats in (4) and (5). Products should be fit for purpose, and therefore problematic bugs (particularly security related) should be fixed even after purchase, for a reasonable period. If your app breaks after an OS update because it was relying on undocumented behavior, I'd say it should still be fixed.
But I think one of the problems here is the inflexibility of app stores. What about the Jetbrains model? As soon as you pay for N months (over time or upfront) you get a perpetual license for that version, and for every subsequent version released while you were still paying. Could you do this on the App Store?
- kartickv 9y agoMaybe you're okay with these, but others aren't. No matter what payment model you chose, some people will be pissed off. Maybe developers should ignore what an angry minor claims, try it out, and see what actually works. We're certainly doing that with our camera app, Noctacam (noctacam.com. It will be subscription-only, at 49 cents a year. We'll see how it goes compared to an upfront payment. The JetBrains model still has all the issues I pointed out above. Which is not to say that it doesn't have other benefits. Every payment model has its problems.