The reason we haven't done it is that it's much more complex than people know, and that's okay, it's our job to think about complex problems, but the App Store has reached so many successful milestones without it because the business model makes sense to customers. And the upgrade model, which I know very well from my days of running many large software programmes, is a model from the shrink-wrapped software days that for some developers is still very important, for most, it's not really a part of the future we are going.I think for many developers, subscription model is a better way to, go than try to come up with a list of features, and different pricing for upgrade, versus for new customers. I am not saying it doesn't have value for some developers but for most it doesn't, so that's the challenge. And if you look at the App Store it would take a lot of engineering to do that and so would be at the expense of other features we can deliver.For example, the App Store has one price for an app, when you see it, you see if there's a price on it, that's the price. It doesn't have multiple prices for multiple tiers of customers so to engineer that in, it's not impossible, but a lot of work for a small segment of software that we hope for many of them, subscription pricing is a better model, the one where the customers are comfortable with. So we'll keep talking to developers about what's most important on their list, we want them to keep telling is if that upgrade pricing is high on the list or not, and we'll keep an open mind to it, but it's harder than people realise.
Gast
