5 ms·
'Cash cow' sales model for a macOS app
- walterbell 8y agoOne question about this model: does the client app need to contact the developer’s licensing server on every app start, or after every app upgrade, or only at the time of in-app purchase? If there’s only a one-time “phone home” to the license server, this seems like a good revenue model that balances the needs of users and iOS developers.
- Rjevski 8y agoIn-app purchases are handled directly by Apple, so you can do away with a licensing server and just enforce licensing on the client.
- walterbell 8y agoBut they are allowing all clients to get new binaries (with bug fixes and new features) while limiting them to features within a rolling 12 month window from time of purchase. Apple doesn’t have the ability to gate features that way.
- ezekg 8y ago> In principle, it’s all pretty straightforward. Of course, the devil’s in the details. I was quite surprised how much work was involved in getting it all working. Probably 3–4 months all up. And that's why I built https://keygen.sh https://keygen.sh, for those that would rather not spend months building a licensing server in-house. I did this one too many times. :)
- userbinator 8y agoAnd that's why I built https://keygen.sh https://keygen.sh, for those that would rather not spend months building a licensing server in-house. For a second, I thought you were the owner of the .us site, reincarnated it under a different domain, and trying to imply that crackers would create a keygen for your software anyway. But speaking as someone from the other side ;-) any centralised software protection is going to be dead-easy to crack since the checks and ways it makes them are going to be nearly the same between all apps that use it. FlexLM is an existing example of this.
- ezekg 8y agoI agree that all software protection is able to be cracked, but I wouldn't say it's "dead-easy" just because it's centralized. And actually, Keygen is a little bit more unique in that case, because I don't supply any client libraries, and you can also put Keygen behind your own domain (similar to how you would put Stripe behind your own domain). So every piece of software is going to implement things differently. In addition, you can implement public key signature verification to prevent MITM attacks (each account gets their own 2048-bit RSA pub/priv keys). In the end, the cracker will likely need to spend some time figuring out how your unique piece of software utilizes Keygen, and that will deter the majority. But like I alluded to, in the end, all software is crackable. There are certainly those who won't stop at the roadblocks. But there's not a lot I can do in that case, especially just being an API. It's more down to implementation. ;)
- cprayingmantis 8y agoI had to read this very carefully to determine if it was parody or not. This seems just like the old system of selling software. Get a free demo, sell the actual software, 12 months later add more features rinse and repeat. There will always be hold outs content with their feature set but there will always be people on the leading edge and it all balances out but this doesn't seem like anything particularly new or novel.
- albertgoeswoof 8y agoYea this is the way a lot of enterprise software has been sold for decades... especially useful if there's a cost to the software company for delivering upgrades (e.g. shipping CDs and installing it), you only have to support for 12 months and after that you're off the hook, if the client doesn't pay up.
- danpalmer 8y agoIn this model the user continues to get bug fixes (and likely new OS support) even after their licence expires.
- nodamage 8y agoBug fixes make sense, but I wonder if it is reasonable to expect/provide perpetual OS support based on a single purchase?
- JumpCrisscross 8y agoHow does one differentiate fixes and feature? For example, suppose a new TLS standard is adopted. This requires work to implement. Is the change a fix or an upgrade? Will the team be indefinitely required to issue updates to the old TLS? I like the agenda-pricing concept. But it feels like a poor-man’s compromise for a subscription. Why not permit downloads of an executable any time a sub is valid?
- jarfil 8y ago
- headcanon 8y agoRenoise (https://www.renoise.com/ https://www.renoise.com/) is sold on the same model. Each purchase guarantees free updates for one major version cycle (if you purchase v2.8, you get free updates until v3.8). Might not follow semver rules, but it seems fair to me.
- antaviana 8y agoI think that pure subscription is the only sustainable model. If the incentive for a new customer is the same as keeping an existing customer, you aim for the right product. I find permanent license models are pyramidal and/or foster featuritis.
- danpalmer 8y agoI disagree. I’d never subscribe to an app whose value isn’t directly tied to the subscription nature. I’d subscribe to Dropbox for example, as it’s an ongoing service, but a text editor? No. I realise there are some small ongoing costs like support, but customers know when the value doesn’t align with the pricing and they don’t like it.
- antaviana 8y agoIf you are unable to extract more value than the cost of the subscription, then it is a bad investment, otherwise it is a good investment with more long term chances for you to extract value from it.
- girvo 8y agoIf it’s a one-off payment, you have your lifetime worth of chances to extract value. So I’m not following your point here, can you clarify?
- antaviana 8y agoSubscriptions have higher chances of survival than permanent licenses because developers have intentionally deferred revenue. So 6 years from now, the motivations to continue operating the business will be higher by a team selling a subscription at $99/year than a permanent license at $299. This way your workflow relying on that tool has higher chances to survive new operating operating systems, new formats and other forms of obsolescence. I liked Microsoft Money but it is not anymore around. Had it been Money 365, it would still probably be around.
- 8y ago
- dep_b 8y agoThat’s a ton of different combinations of flagged features that might or might not exist for a user and almost all possible combinations need to be tested.
- jarfil 8y agoIf I understand it correctly, when a user pays they get all of the features available at that time. So there could be users with only feature 1, and users with features 1, 2 and 3, but never a user who only had feature 3. That reduces the number of combinations from O(2^n) to at most O(n), and you could keep track of which older features no one has, or offer periodic free/discounted updates to reduce the amount of different versions out there.
- jakobegger 8y agoOh my god I get a headache just thinking about all the feature flags they'll have to maintain, and all the copywriting to describe each feature, and all the support emails from people asking which features they can use... What are they going to do when a new feature makes another one obsolete? Keep both? What if they fix a bug in the new version, do they also fix it in the obsolete version? This sounds like a major maintenance chaos a few years down the line. They'll need to keep adding individual features to incentivise frequent re-purchases, so they'll end up with hundreds of variations of the app, all depending on when you bought it... Thinking about this makes me so happy about the pay-once model of my apps, I'm so grateful that it works, and that I don't need to squeeze every penny from my customers.
- on_and_off 8y ago>pay-once model of my apps it is a pity that people don't like subscriptions because it seems way more sane than fuelling development only with new customers. For some apps it works to pay once but if it is something that is constantly developed and/or has server costs, this is far from ideal
- jakobegger 8y agoAs long as you make a decent app, there will always be new people that want it. And the larger your userbase, the more word of mouth advertisement you get. So it might not be the best idea to keep your userbase small by requiring them to pay again and again.
- heckanoobs 8y agoI think you can get by with adding timestamp support to a single feature flag. So the code has IS_PREMIUM everywhere but when you add a new use of it you also manually record the time. Since you know the expiration time of their license you can always determine what features are unlocked based on that. Then you just develop the app as any other demo-with-upsell app. Users even continue to get bug fixes and other updates after they let the license lapse. In cases where features are removed, combined, refactored, you'll have to be judicious about what timestamp you apply to the refactor. I would resolve in the customer's favor personally. Edit: Thinking on this more you might also want a rule like feature flags are only implemented at the view layer. That way your biz logic never gets tripped up on flag checks as features cross paths under the sheets. So its does require a fair amount of code discipline to pull this off
- orasis 8y agoThese guys are fooling themselves. If their app provides ongoing value, then subscriptions are the way to go today - it's just a matter of charging the correct price for the perceived value the consumer is receiving.
- digi_owl 8y agoSoftware, like books, only has a market as long as the distribution is a pain in the behind. Once the distribution is as easy as the press of a (virtual) button, the market basically evaporates.
- kennydude 8y agoSetApp is a great way to do subscriptions on macOS. It has lots of apps, and lets me try them whenever I want without really comprimising on much.