> What does count as "a lot of back-end work" that's valuable to you? By way of examples, something like a weather application or access to content. Weather d

> What does count as "a lot of back-end work" that's valuable to you? By way of examples, something like a weather application or access to content. Weather data is, at least until the end of humanity's existence on Earth, ever-changing and in need of update. > Why are subscriptions bad and what would your solution to this be? Because I do not want to wind up in a situation where an app developer suddenly turns on subscriptions and hides features of an app behind it, on the back of an opaque update. Plus, for most apps I am quite happy to pay for a particular version and be done. (I have no problem with paying for applications.) I want the finality of the transaction, that I've given my $5 or $10 or $20 or what-have-you a single time and our business is done. Application makers have done this since time immemorial, sometimes releasing complimentary bug fixes, other times not. I just don't like the idea that in order to retain access to a program that does all of its work on my device, I have to keep paying rent for it. Like the app at issue here, where it was doing what the user wanted and then poof, a change that cannot be reversed. I also understand that the current model on the app stores is not conducive to one-and-done application purchase transactions. Apple doesn't make it easy to do upgrade-by-version pricing, for example. In-app purchases are available, but they're not (by default, or nearly as widely) sharable on the family-level like outright purchases are.