5 ms·
Well, one thought about your pricing model - you’re thinking that it might need work in the future, but you’re charging each month without delivering any additi
by nepthar 2y ago
Well, one thought about your pricing model - you’re thinking that it might need work in the future, but you’re charging each month without delivering any additional value to customers. How about charging additional money for each new major version, corresponding to either new feature development or support for new versions of the OS?
- mrtksn 2y agoHow do you implement that?
- wingerlang 2y agoI don't think App Store supports that. But if you're interested, it's a planned feature in my macOS license management SDK (padlockSDK.com - pricing is placeholder, its free until I know if it's of interest for people).
- mrtksn 2y agoThanks, I will check it out
- NullifyNAN 2y agoThe Due app does something like this. Basically it’s 1 time fee + subscription. The day you buy the app, you get every new feature for the next year and every previous feature. If a new feature is added, you can subscribe for $5 a year. Upon subscribing, you get all new features since your subscription lapsed. Blog post here: https://www.dueapp.com/blog/future-of-paid-upgrades.html https://www.dueapp.com/blog/future-of-paid-upgrades.html
- chris_st 2y agoLoopy Pro does this as well.
- cfn 2y agoThis is a big issue with the App Store. Either you charge a subscription or you charge a on-off and all upgrades are free forever.
- nepthar 2y agoOh wow, I actually had no idea that was the case. That definitely throws a wrinkle into things
- zeusk 2y agoThat's definitely not the case, Apps can lock new features behind IAPs and keep charging for new features while sharing bug fixes.
- xattt 2y agoWhy can you not create a new app with a similar name but name it v2, 3, etc? Things and many others did this.
- deleted 2y ago[deleted]