Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Or, "We release updates to our app every two weeks. Thanks for using our app!"

Why even bother having release notes at all if that's what you're going to say?! They might as well just put ":)"

Yeah, Facebook release notes come to mind when you say that...
[doublepost=1465417016][/doublepost]
John Gruber adds a good note. The subscription split will change after the first year, to 85/15 from 70/30.

That's a really good move, and very fair.

Also, at the bottom of his article, he put:

"Last but not least, the fact that these significant — dare I say dramatic — changes to the App Store didn’t make the cut for the WWDC keynote makes me damn curious about what did make the cut for the keynote."

Now I'm even more excited!
 
... release notes when releasing a new update. Make it mandatory to state what's changed.
The one that really gets me is the developers who are clearly using Agile methods like Scrum*, who use their development methodology as an excuse not to list the changes, instead saying, "we release a new version every two weeks" (yes, you do, but stating that is NOT release notes, that's handwaving while avoiding the question, like a politician).

The worst offender (at least for a while, I think they've changed their text) was Facebook, who would say "To make our app better for you, we bring updates to the App Store every 2 weeks. You can update the app automatically (without checking back here) by going to Settings > iTunes & App Store > Automatic Downloads and turning on Updates".

Translation: "oh, don't worry your pretty little head, these are big confusing things for us smarties to deal with, just push this button and then that one, and you won't have to be confused by seeing this any more." I know how to read release notes, thankyouverymuch, and I want to know what changes to expect in the program - that's EXACTLY why I process the updates by hand, rather than turning on auto updates.

*: Agile methods like Scrum are, in and of themselves, a very good thing actually; they involve choosing a set of fixes/improvements that can be implemented and tested in a fixed period of time - often two weeks - and coding and testing those improvements, and then making a new release; great way to get a continual trickle of updates instead of development getting bogged down for months/years at a time.
 
  • Like
Reactions: SMIDG3T
I'm not sure that the subscription is going to be an option for the end-user if the developer chooses to go that route with their app. I don't recall reading anything that said a developer could give the customer the choice to either pay an amount up front for an app or have a subscription fee charged every year. I think it's an either/or scenario depending on what the developer chooses to do.

If, say, 20% of the 30 or so apps that I use consistently on my iPhone went to a subscription model and they each charged $5.00 a year, that means (if I understand what Schiller is saying) I can either delete those apps if I don't want to pay the fee or I can just accept the fact that I now have to pay $30.00 more every year for the privilege of using those apps -- regardless of whether or not the developer releases four upgrades per year or no upgrades at all.

Vote with your wallet.

TL;DR: This is only valid for new users.

Absolutely true, assuming that you don't already use the software in question. It's a case of "it's easier to stay out than to get out." I for one will pretty well never go in for a subscription service that doesn't offer a hell of a benefit, with no enormous downside. So, I do have a subscription to Apple Music, for example, but if I want to end that subscription, then I can, and I lose access to the catalog. I do not lose access to my bought songs and whatnot--not a huge pain. Once upon a time I had cable, but I cancelled because I only watched little and it wasn't worth it, so I lost cable, and it was no big deal. Again, no personal hit.

However, I have used two software packages in the past that have gone SaaS. YNAB and TextExpander. In both cases, I'd been a user for many years, and very happily so. I updated every time there was an update, and I bought the major upgrades. The result of that was that I had a crap-ton of my data invested in these apps--workflows that have been ingrained for years, processes that worked for me. And then the developers decide that they're going SaaS. They essentially have me by the balls at that point because if I simply say, "well, then I just won't do it" I lose my data (or at least the ability to work with it as I have been forever). In the case of these packages I was paying something like 40 bucks a year for both between major revisions where I'd pick up the most recent for upgrade pricing, even though I didn't HAVE to. The subscription model has me paying over 150 dollars a year Canadian just to get and use my own historic data. Having my data held hostage and paying that is extortionate (let's forget for the moment that YNAB has its head so far up its arse they can't even import the old data yet in spite of promises to be able to do so for six months, but I digress). Even if you argue then that I should simply prioritize what apps I truly NEED, thereby leaving other software out in the lurch, I resent the fact that I need to say, "please sir, may I have and use my data" to a company every month. If I buy it, I want to own it. I don't want the chance that someday for whatever reason all of my data simply vanishes because I can't pay (the whole 'skip Starbucks this month' argument is such trite bullcrap).

Anyway, I'm ranting. Subscription bad. Owning good. Will not subscribe to anything mission critical, and am unhappy Apple is espousing this.

If software is mission critical, there shouldn't be a problem with subscriptions. Also, nobody owns software. You buy a license to use it. Plus, let's not pretend subscriptions aren't in apps already. The difference this will make is that it makes it possible to have a recurring instead of bugging then every so often to pay again.

Look at Overcast for how this works right now and how it might work for most apps in the future.
 
No that is not what I am saying at all...

If the App is worth $10+ then they should not charge me $1.99 in the first place and come back later like a Junkie begging me for more.

The only reason to charge $1.99, or give it away for 'Free' when it is not 'Free' or not worth $1.99 is to drum up sales by misleading the consumer.

Yes, Photoshop and Office 365 are subscription and I use neither. I use QuarkXpress, a PhotoShop alternative and Office 2011..

The fact is most people don't want to pay for the value of software. The market has devalued it to nothing and complained how quality went down.
 
As a developer, I want less stuff to deal with. Auctions give me goosebumps.

Why not simply having every second entry of the search result list being a random entry from the whole list instead of always using relevance sorting in strict descending order? This gives everybody a chance. One line of code for Apple, makes Indies happy, keeps the user review rating healthy.
 
I would much rather see upgrade pricing, but subscriptions would work as long as they aren't overpriced or abused. I can already see some developers abusing this. Double dipping by making us pay the subscription for the app and then sticking ads in the app as well.
 
I can understand the subscription model. I don't like it as I want to be a cheapskate, but developing an app for a very long time is a drain on developers, I will just be very selective with what I use. Nothing wrong with that.

Think they can work for content style apps but no one is going to pay money for a task list app or calendar on a rolling basis when there are other free options.
 
I don't actually mind the idea of subscriptions for apps that merit it, both by being really exemplary/worthwhile apps, and by being updated often, with useful improvements, especially if the apps have some ongoing costs for the developer (e.g. their own back-end server if they really can't do what they need via iCloud and such). In this category I'd put (in no particular order) things like, 1Password, Overcast, Drafts, Day One, OmniFocus, Pythonista.

HOWEVER, I expect to see a lot of developers having a substantially overinflated sense of their app's worth. I'm guessing a bunch of apps that I bought for $5 and are worth $5 are going to decide that they should be $5/year, without doing anything extra to merit the ongoing cost. And I expect I'll be throwing out a bunch of those apps. (I also expect to see some folks who have one good utility app to offer it instead in a subscription bundle of that app plus their seven other not-very-good apps, harkening back to the days of music available only as albums, where a band would have two good songs and six filler songs you'd be obliged to buy to get the good two).

I'm hoping that'll level out after a few months, once developers see the repercussions, so that only apps that really merit subscriptions go with that model.

It will be, hmm, interesting, to see exactly how they handle apps that transition over - say I bought a $15 app a year ago and it moves to a $5/year subscription model: it'd be nice if it applied the purchase price to the subscription, pro-rated for when I bought it, and thus decide I've got another 2 years already paid.

As well, there's a substantial pain point if a developer converts an existing to the subscription model, then finds that they overestimated their app's value and so they switch back to a plain purchase model - how does Apple handle people who purchased it before the conversion (that's not too hard, they just keep it), and how do they handle people who purchased it while it was a subscription (possibly for a lower price than the previous full purchase price).
Good points!
Particularly interesting:
I also expect to see some folks who have one good utility app to offer it instead in a subscription bundle of that app plus their seven other not-very-good apps
Sounds like Cable TV for Apps.
 
Also, at the bottom of his article, he put:

"Last but not least, the fact that these significant — dare I say dramatic — changes to the App Store didn’t make the cut for the WWDC keynote makes me damn curious about what did make the cut for the keynote."

Now I'm even more excited!
I wondered about that too, but keep in mind that Apple's intended audience for WWDC is (only) developers - not the population at large. By announcing it beforehand via a techy-but-not-specifically-developer-oriented venue, this news gets the additional/wider coverage it deserves. And, yeah, it doesn't get lost amidst the WWDc coverage on Monday (with Tim Cook going all Oprah - "and you get an Apple Car, and you get an Apple Car, everybody gets a free Apple Car!").

I'm excited too. :D [ no, I won't be at WWDC (only watching online) and no I don't expect there to be any special prize under the seats, and no, I don't expect Tim to dress up like Oprah. ]
 
Last edited:
The fact is most people don't want to pay for the value of software. The market has devalued it to nothing and complained how quality went down.

I agree, however I prefer choice over misleading the consumer. IAP's devalued the market IMO. Who allowed IAP's...? So a self inflicted wound IMO.

If the price is not right then the consumer always walks away. It is when they try to fool the consumer, or take them for granted, is when I have issue.

For example, do not offer to sell me a new Mercedes for £1.99 only for me to find out once I have the keys and driving out the showroom door that I need to pay [as I drive] £5 a mile for life, or the car stops working.
 
  • Like
Reactions: DiceMoney
Does this pave the way for an Amazon Prime Apple TV app?
I'd really like that to happen, though I suspect Amazon is looking for an even better deal than 70% for the first year and 85% in subsequent years. I still look at it as, I already subscribe to Amazon Prime, I already have an Apple TV, you already made an iOS app, just port the damn app to the very-slightly-different tvOS already.

The whole bit about "we can't sell the Apple TV in our online store (nor can we let any third-party seller list it in the store), because that would just be too confusing for consumers, since it can't watch Amazon Prime video"... that is so much BS. Aside from Amazon themselves being the cause of the problem, it's clearly an attempt to prop up Fire TV sales. Do they ban phone accessories with Lightning connectors, because they can't be used with the Fire phone? Do they ban every CD/DVD/BluRay that is available for streaming on the Fire TV? It's an uncharacteristically baldfaced lie from Amazon, for whom I otherwise have considerable respect. If they'd said, "no, we're not going to sell it because we have a competing device we'd rather people would buy", that'd be annoying but understandable. But this, this is just shameful.
 
  • Like
Reactions: chiefsilverback
The fact is most people don't want to pay for the value of software. The market has devalued it to nothing and complained how quality went down.

What I'm afraid is going to happen is that developers that used to charge $4.99 to own the app outright are now going to charge $4.99 per year and they're not going to offer enough new features for the vast majority of customers to justify paying the yearly subscription fee. The app is then going to be given a bunch of 1 star reviews and that will force some prospective buyers to stay away.

Apple and developers need to tread very carefully here. This has the potential to blow up in Apple's and developers' faces pretty quickly if they're not careful.
 
By the way, on the topic of "why is this coming out before WWDC", John Gruber's quote from Phil Schiller's phone call to him is enlightening:

“We’re doing something a little different this year. We’ve got a bunch of App Store/developer-related announcements for WWDC next week, but frankly, we’ve got a busy enough keynote that we decided we’re not going to cover those in the keynote. And rather, just cover them in the afternoon and throughout the week. We’re talking to people today for news tomorrow about those things, in advance of WWDC, and then developers can come and be ready for sessions about these things, with knowledge about them before the conference. We haven’t done this before, but we figured, what the heck, let’s give it a try.”​
 
Last edited:
How about some essentials like info about a sale on some apps of your wishlist? Price change of a watched app etc.
bring some of the usual stuff to the app store.
 
What would really help is upgrade pricing! Seriously; that's a no-brainer feature that I think just about every developer with a paid app supports.

Not just upgrade pricing, but you'd also have to have a way to migrate everything over to the new app that you just upgraded. Upgrades are really quite a pain technically.

Apple sees subscriptions as the same thing as upgrades, except its mandatory - you don't get to choose not to upgrade this year and you are forced to keep paying not just for upgrades but to use the app. However, if this is what the App Store is going to offer, then subscriptions so be it.

What would be cool is if you could pay $10 a month and get "x" apps in the "Silver" category for example.
[doublepost=1465421510][/doublepost]
I'm fine with app subscriptions, i'd like trial periods on paid/subscription apps

Auto-renewing subscriptions have had the option for that, but now every app will have access to that. So you signup for a 1 year subscription - but you get x weeks for free trial first. Unsubscribe before that time and you pay nothing.
[doublepost=1465421664][/doublepost]
What I'm afraid is going to happen is that developers that used to charge $4.99 to own the app outright are now going to charge $4.99 per year and…

I can agree that pricing is going to be difficult. However, the problem is using past pricing as a guide. For example I know apps that used to cost $30 new and $15 a year for upgrades. On the App Store they just sell it for $15. They might consider a subscription of $15 a year and instead of holding back major new features for each major release, those major features are now developed throughout the year.

Subscriptions do offer positives, along with the negatives. I wrote about them here: http://pocketinformant.com/the-app-...-calendar-a-la-carte-or-subscription-fits-in/
 
Too many subscriptions in the world. I would certainly buy apps on a whim (for example I have about 5 different PDF readers - they all have strengths and weaknesses); if it becomes subscriptions, I'm just going to choose one and ditch the rest.
 
What would really help is upgrade pricing! Seriously; that's a no-brainer feature that I think just about every developer with a paid app supports.

I believe that already exists, where they abandon version X of the app and you need to pay to get version X+1. Also, in-app-purchases could in theory cover new features.

And really, that's not even how software is, or should be made, anymore, where months and months of development are coalesced into a single upgrade that maximizes the risk of bugs, and keeps features out of users' hands the longest. The industry has long since moved to agile updates in a short time period, where there would never be one big moment for the user to decide to upgrade. That old way also drastically increases development costs, since multiple versions need to be concurrently supported, along with data migrations, security updates, documentation, etc. Really, getting improvements as fast and inexpensively to users is the best way, and that's just not compatible with upgrade pricing.


Subscriptions and ads? No thanks. I just want buy an app once with no ads or iap. They should also implement a try before you buy feature.

I agree, I personally prefer paying up-front, and not using IAP or seeing ads. But likely Apple doesn't allow time expiring full versions, since that introduces two buy decision points, which is bad salesmanship. While it would reassure users that the software behaves as advertised, it also encourages a wasteland of non-functional apps on devices that would make for a bad user experience. And likely be mostly abused by users who temporarily need an app and are avoiding paying for that short term need.


Paid upgrades never made sense. If you're a smaller developer you should be constantly delivering new features and fixes. For those that support their application well they'll succeed at subscriptions. For lazy developers they won't hit that year mark for many subscribers and they won't be able to leverage the savings.

Agreed. Plus, some types of apps are just more conducive to subscriptions, and some types the users just won't accept subscriptions. Either way, the market will sort it out, as you say.


What happens when the app's developers go out of business, or quit, or decide they no longer want to support the app? The app will stop working and I will no longer be able to use it.

If I buy an app outright, I can use it as long as it continues to function with my current OS. (And even then, I can always choose not to update the OS if I really rely on the app.) I am not bound to the whims of the developers or their financial situation.

There's also the scenario of developers removing features from apps in "updates". Maybe I don't want to update the app because I don't like changes that have been made. App subscriptions will force me to "update" whether I want to or not.

There are far more negatives with app subscriptions than positives.

Upgrade pricing is the solution here.

I think you raise a good point about removal of features, as I've experienced that, since app developers are under pressure to add features for experienced users, while keeping features streamlined for new users. But, updates are different that subscriptions. I believe it would be possible to turn off automatic updates, while maintaining a subscription.

As it is now, if an app is no longer actively developed, it's a total crap shoot if the next iOS update will break the app. But one thing is for certain, which is that uncertain revenue is the most likely cause of the developer going out of business. The question we'll need Apple to answer is what happens with subscription apps from defunct companies. Can anyone here say what happens to existing apps once a company stops paying their $100/year?


What I'm afraid is going to happen is that developers that used to charge $4.99 to own the app outright are now going to charge $4.99 per year and they're not going to offer enough new features for the vast majority of customers to justify paying the yearly subscription fee. The app is then going to be given a bunch of 1 star reviews and that will force some prospective buyers to stay away.

Apple and developers need to tread very carefully here. This has the potential to blow up in Apple's and developers' faces pretty quickly if they're not careful.

Keep in mind that we've long since bottomed out the race to the bottom for pricing, so developers know they can't simply overcharge for apps, that users won't bite.

What I think is more likely is that in year 1, apps will become cheaper. Right now, developers have to charge a rate to cover several years of development, but with subscriptions, they can tie rates to the cost of each year of development, so I would expect a $5 one-off app to become a $2/year app, for example.
 
Something tells me this will suck... the only ones to benefit from it is Apple and deep pocket developers.
 
What I'm afraid is going to happen is that developers that used to charge $4.99 to own the app outright are now going to charge $4.99 per year and they're not going to offer enough new features for the vast majority of customers to justify paying the yearly subscription fee. The app is then going to be given a bunch of 1 star reviews and that will force some prospective buyers to stay away.

Apple and developers need to tread very carefully here. This has the potential to blow up in Apple's and developers' faces pretty quickly if they're not careful.

That's a problem developers need to solve. But that's not to say subs are bad.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.