8 ms·
Have you tried purchasing the "latest" version of World of Warcraft? You can't. There is no standalone "latest version". You have to purchase the original, a
by Terretta 14y ago
Have you tried purchasing the "latest" version of World of Warcraft?
You can't. There is no standalone "latest version". You have to purchase the original, and each version since, and finally the current version.
Correlate those game content / game mechanics updates with In-App Purchases, and it's clear how someone could offer "major upgrades" if they stop thinking in terms of version numbers and start thinking in terms of actual upgrade features. (See "Navigon" for an app that has done this.)
And if the entire app architecture changes, make a new app.
- 89a 14y agoThink the problem is policing it. Apple doesn't want it to become the standard that people are being charged for bug fixes every version.
- cloverich 14y agoCan't people decide not to purchase the app then? They have a content review system - 10 recent 1 star "Bug fixes cost $$$" and the app is dead, no? Or am I overlooking something?
- ricardobeat 14y agoThat's right. Then the app is dead and users are dissatisfied. No one wins.
- jawngee 14y agoThe problem is getting customers of version 1 onto version 2. There is no way to do this with MAS. I have a mechanism built into Shave so I can push "news", but it's annoying and bad user experience.
- spaghetti 14y agoWhy can't you update the app and hide most of the new features behind an in-app-purchase paywall?
- modernerd 14y agoNew users who purchase the updated app would have to pay again to get the latest features.
- spaghetti 14y agoI think the following set-up avoids that problem: app is always the same price to download and has a few basic features unlocked. App has an upgrade view or screen where users can unlock additional features via in-app-purchase. It works like this: developer releases the app for, say, $10. People buy it and use the basic features for a while. So far there's no upgrades available. Developer codes up a premium feature and updates the app in the store. Existing users can use the app as-is with the basic features that came with the $10 price tag. Existing users can also make an in-app-purchase for, say, $5 that unlocks the premium feature. When new users download the app for $10 they just get the basic features. Since another "version" of the app is available the new users can just buy the premium features if they so choose. Fast forward to version 5 of the app. Now there's 4 upgrades available via in-app-purchase. However users are only prompted to purchase the next version based on their in-app-purchase history. I don't think there's a problem for new users who purchase the updated app.
- jarek 14y agoThis does away with everyone-is-on-newest-version paradigm of automatic updates that makes support easy - in fact, it makes it much worse. Instead of five old versions of the app, you might have 1 base + 12 permutations = 13 different combinations of functionality to support.
- spaghetti 14y agoGood point. This approach probably wouldn't work for some apps. However if the app lent itself to a very modular design it could work. Certainly would take some creativity on the developer's part. For example premium features that are troublesome if only some people have them could be included in a free bug-fix update to make things easier.
- nsxwolf 14y agoWhy not a "fat" app? Always include two major versions in one binary, instead of putting the new features behind a paywall. Have an IAP purchase that just configures the app to run "Side B" from then on. edit: no, I guess that does not work per below.
- illumin8 14y agoDevelopers could very well re-architect their application so that when you download the update to v2, you have to unlock the new features with an in-app purchase, but to be honest, it's a lot of extra work for the developer, and there is no way to make it less painful for the users, who will feel like they are getting nickel and dimed by the developer. Also, for those users that are brand new on the v2 version, it's a very bad experience when they have to immediately buy an in-app purchase just to unlock functionality that should be included. If you drop the price of the v2 version to accomodate this, then your original v1 userbase will complain that they paid twice as much. Here's an example: v1.0 of App X sells for $9.99 on the app store. Users buy it and are happy. v2.0 of App X comes out and to unlock the new features, you must pay $4.99 in-app purchase. Developer drops the price of the app to $4.99 so that new users don't have to pay $14.99 to get all the features. New users now complain that they have to immediately make an in-app purchase just to unlock the software - they don't notice that it's half price now because they never bought it previously. Existing users complain that they paid $9.99 and are now being nickel and dimed for updates, when the price is cut in half now. You can't win. Unfortunately, Apple has create a model that makes a lot of profit for them, and makes it relatively painless for the end user, but it's a model where the developers suffer and can't really support the large applications that receive many new features every year.
- chc 14y agoI think you misunderstood. He's suggesting that instead of releasing v2.0 on the App Store, you release an in-app purchase option in the original app that upgrades it to v2.0. A similar idea would be to release new features a la carte as in-app purchases instead of releasing new numbered versions. I'm not sure if the marketing hit would be worth it, but it is one way to a consistent revenue stream.
- DigitalJack 14y agoDiner Dash follows this model. They update the app periodically and add new content available via in app purchase.
- pgeorgi 14y ago
- mistercow 14y agoThere are a lot of problems with that idea, but the biggest I can see is that the user experience is horrendous. You're basically describing a world of itemized crippleware, where buying an app that's more than a few years old involves a half hour-long process of adding on feature packs.
- deleted 14y ago[deleted]
- retr0rocket 14y agodid you just compare a game with a 15$ subscription and 40$ expansion packs for major updates and lvl bumps to a 10 dollar app? do you realize how asinine that is and how dumb you sound? if i want to get to current content in WoW i would of had to get Vanilla(50$ at release) + burning crusade (40$ at release) + wrath of the lich king(40$ at release) + cataclysm(40$ at release) PLUS every month im paying 15$ on subscription if i just buy vanila i would be limited to 1-60 content, not allowed full access to any of the later continents and cities, skills, talents, cant pvp properly, not allowed in arena, cant do any endgame, and am generally wasting my time. how is that at all conducive to what you are saying? for any real application that does work or major game that requires constant updates you cant expect support and update for 10$ that's completely unfeasible. you sound like someone who never played world of warcraft in his life, and it baffles me how you came up with such a nonsensical rebuttal
- tg3 14y ago>do you realize how asinine that is and how dumb you sound? That was unnecessary and did not add to the conversation. And I'm not sure that I understand your point. Parent comment is saying that apps can follow the WoW model to create a consistent revenue stream without paid version number upgrades. As you mention, "for any real application that does work or major game that requires constant updates you cant expect support and update for 10$ that's completely unfeasible."
- retr0rocket 14y agoyou cant follow the wow model, the wow model requires constant fees every month, thats my whole point, when you play wow you pay blizzard constantly, and anytime there is a major update you pay another large chunk. you cant do that with a video editor, and its not like maps where you can segregate off chunks of content. like i said completely asinine, and unequatable in this circumstance, the fact that so many people agreed with such an obviously flawed argument speaks volumes.
- grayprog 14y agoHaving version 2 as in-app purchase means your version 2 app has to include version 1 in it. Good luck with implementing that. What if my version 2 is a major rewrite and I change software architecture or want to use new features. Can you imaging writing an application with 2 different interfaces, database formats and feature sets, just to make it possible to upgrade with in-app purchase? No, thank you.
- cube13 14y agoWorld of Warcraft is a bad example of this. The client you have downloaded is always patched to the latest version, even if you haven't bought the expansions. Each expansion unlocks content. So once you buy The Burning Crusade, you get access to the Outlands zone. That only matters if you have a character that's level 58 or higher. Blizzard redid the entirety of the Vanilla WoW experience in the Cataclysm expansion. Even if you did not buy that expansion, the level 1-60 are still the new content.