3 ms·
> People expect updates once they've purchased an app for a few bucks. ... and the App Store model does not allow a developer to e.g. maintain three different
by mschuster91 9y ago
> People expect updates once they've purchased an app for a few bucks.
... and the App Store model does not allow a developer to e.g. maintain three different branches of a product (oldstable, stable, beta), with purchases tied to the branch. This makes a "classic" release flow like 1.0 is released, then 1.1 is released, then 1.2, then 2.0 (with new features, whatever), and then a patch 1.3, impossible.
Unfortunately, this "only ever have a single released/maintained version" approach (that was famously pioneered by Apple in iOS itself!) has caught the entire industry - there is no way to avoid e.g. a major update because it brings a royally fucked up UI, lost/rearranged features or whatever without risking security issues.
This is really really bad for enterprise customers where things like "UI overhauls" can lead to a massive, expensive training for all the users or at the very least an increased amount of helpdesk tickets.
- comex 9y agoActually, many developers do exactly that by releasing each major version ("branch") as a separate app.
- mschuster91 9y agoThat's a hack though. Also, how do you do stuff like giving out "upgrade discounts" or discount vouchers? That's not possible at all.
- Razengan 9y agoI believe some apps have done that by requiring some sort of proof of purchase for an older version, and maybe paying the developers directly at a discount, who then prove the user with a code to redeem on the App Store. Convoluted currently, but not impossible.
- Razengan 9y agoReleasing major versions as separate apps is actually desirable for a number of reasons: • The users decide if and when they want to upgrade. • If a trial for a newer version is available, users can try it out before upgrading. • Users can keep older versions if they prefer the older UI etc. They’re not forced to like all and any major changes just to keep using the app. There’ve been plenty of [in]famous cases where people complained about new versions of popular apps and websites. • Generally a predictable timeframe for yearly updates. • Users don’t have to pay every month even when an app is getting no updates. • Developers are not under any pressure to release updates for the sake of updating to justify a monthly subscription. Subscription-based software generally loses some or all of these advantages. Subscription-based apps seem to favor developers more than users. Greedy developers, in my unsugarcoated opinion.