As Ken himself notes in the article, it worked for "retail boxes" but that model is now obsolete. Upgrade pricing will almost always lead to an abusive relatio

As Ken himself notes in the article, it worked for "retail boxes" but that model is now obsolete. Upgrade pricing will almost always lead to an abusive relationship where the consumer is on the receiving end. Rate-limiting features, bumping major version numbers, setting targets for bi-annual release cycles, abandonment issues of old versions, creative versioning schemes, complex upgrade paths--it all sucks for consumers. All internal conversations around features and releases will also involve revenue assessment, putting business first, consumers second. In-app purchases may require some re-architecting but in the end it's a better fit. All consumers should have the latest core so they get security upgrades through the life of an app and can buy any features al-a-carte that are carried forward. The skeptics should note that web-apps already work this way and it's a lovely model. You don't need to pay extra to load version 2.0 of a website. If it worked that way, it would suck for everyone, even more so when the underlying technology is changing fast (HTML, CSS, browsers, etc).