4 ms·
I think IAP is a pretty kludgy way of solving the upgrade problem in a lot of cases. As a user, I don't want to be nickel-and-dimed for every little feature.
by suresk 14y ago
I think IAP is a pretty kludgy way of solving the upgrade problem in a lot of cases.
As a user, I don't want to be nickel-and-dimed for every little feature.
As a developer, I don't want to shoehorn every change I make into an IAP feature.
Can you imagine if you had to "upgrade" OS X, Aperture, Photoshop, or Office by purchasing a bunch of "features"?
- jimbokun 14y agoWhat's the granularity of an In App Purchase? Could you make the next version of OS X a single IAP? (Serious question, I'm not familiar with the mechanics of IAPs.)
- suresk 14y agoIAP is (roughly) limited to unlocking functionality that exists in the app, offering a subscription of some sort, or offering new content. You sort of could deal with something like OS X Mountain Lion as an IAP, but it would be incredibly ugly - you'd essentially have to ship both code bases, and "unlock" the new one based on whether or not they purchased the "upgrade". IAP works pretty well if you have new features that are fairly discrete and are worth paying for individually. As a substitute for an actual upgrade, it is an ugly hack.