As annoying as this is - and I agree that they should provide an option to charge for upgrades - the problem can be alleviated to a large extent by in-app purchases.<p>Suppose for example you have FooApp 1.x, and you later want to release a major update, FooApp 2. You release FooApp 2 as a separate app for new customers, and provide an update to FooApp 1.x which lets existing customers update.<p>This is admittedly awkward, and can only really work for upgrades where the main new things in the new version are additional features. For apps which have major architectural changes it would be problematic. To the best of my knowledge though this is the best we can do in the context of the current policies.
One issue: how to move data from old app to new - and separate - app? On a Mac it's easy, because everything has access to the full file system. On iOS, apps are blocked from anything outside their "sandbox". I gave up on one desirable iOS app because I'd entered a pile of data in the free version, and couldn't move any of it to the new/paid version.
Btw, I've now dropped over $1,700+tax on Logic. From my original purchase of 4.0 from EMagic that I ran on Windows, Logic 6 post Apple acquisition, Logic Studio 9, and now Logic Pro X.<p>I am totally fine with the $200 pricing which is less than the cost of the previous upgrades. Everyone seems to be forgetting that there was a point when Logic cost $999.
<i>I’d say that this is the best indication of Apple’s intentions and expectations for the App Stores going forward.</i><p>a lot of assumptions made for this one niche product, only on the mac app store, for a product that is receiving an update 4 years after the last version was released.<p>maybe, it's just the fair market value price for a new version of an application?
We did the same a few months ago with one of our products. No one complained yet so I guess people seem to accept it.<p>Though we left the old version in the app store (with a warning in the description for new would-be customers) so people can re-download their old version.
Upgrades are confusing for novice users. Version numbers aren't. While upgrade pricing has been nice in the past, I fully understand wanting to get more revenue from existing users, it just means that the price per version should drop. If customers are truly "loyal" they should have no problems paying full price for an app.
Wait. So if I'm reading this correctly, Apple's answer is being silent? There are much better alternatives here<p>1. Point the old app to the new app, so people know there is an upgrade. Also address the concern of moving data to the newer upgraded app.
2. Provide an subscription model