One aspect that I think some proponents for subscriptions are missing is that subscription pricing, at least in the case of Ulysses, encourages users to pay for promises.
Yeah, I would wager that's true for most (and I'm not just limiting myself to voices in this thread). When the developer bills it as a way to fund a
steady stream of updates - and in my past experience that's been at least one of the reasons provided - and if the customer also looks at it that way, then absolutely. The difference is in the perception of "I'm paying for past work" versus "I'm paying for future work".
It doesn't have to be that way, though, regardless of how the developer sells it.
Whether I pay for major releases or an annual subscription I'm paying for a piece of software that is already useful and valuable to me (or in the case of premium apps without trials,
hopefully will be). Paying for major versions even when the previous one is "good enough", or for the annual subscription when it rolls around, is my way of signalling that the software continues to be useful and valuable to me above and beyond what other options are available - because or regardless of choices the developers have made.
But in neither case do I have any reason to expect the software to continue to develop in a way that is actually beneficial to
me simply due to the way the payment was packaged. The moment the money leaves my account the reasons for paying it are in the past. If afterwards the software
does move into a direction that makes it a worse fit for my needs than something else on the market, that's when paying for the
next version or annual subscription comes to question.
When I bought Ulysses 3 years ago, I knew what I was getting, and I found the $45 to be worth it. If I were to give them $30 today, what would I be getting? They don't have a roadmap or even list of planned features. Are the new updates going to be more blogging platform integrations? Because those hold absolutely zero interest for me, and frankly feel like bloat. Had the app been subscription-based three years ago (we'll pretend I would actually have subscribed, which is unlikely), I'd be pretty miffed that I spent $75 on features that are of zero value
A roadmap is useful - I like information that helps me make more informed choices as much as anyone. But allow me to make an observation:
Even premium apps can have roadmaps, or not. Is this point perhaps more about predictability of future development than how you pay for software?
Regardless of how you pay for a piece of software, that money is gone. If you were not happy with what you got when you paid, then either way you are paying for future development and hope for the best. And potentially end up miffed if things don't go as you had hoped.
This also raises another question - is a roadmap really going to trump what actual, immediate use and value you get out of the software right now?
The answer to that might very well be yes - people value different things. But assuming the roadmap doesn't include things like "we're going to make it slower and more unwieldy", if a piece of software is without a doubt useful and valuable to you now, would you not pay for it if you saw features in the roadmap that don't interest you in particular?
And I mean regardless of if the payment came in the form of "premium" or an annual subscription.
If you're going to do subscription, I think you have to give a roadmap. If I had assurances that this year we'd see CriticMarkup, next year we'd see front matter and MOBI export, the year after that we'd see Vellum integration, etc., customers would be more informed and more comfortable subscribing.
Again, information is useful for making better decisions. But that information doesn't guarantee a decision to pay:
Whether premium or subscription, people might also decide that since those features are what they really need and they're not there yet, they will continue using what they've used thus far (and potentially paid for) because it's "good enough", and then reconsider when the other piece of software is updated with those features.
The problem, of course, is that there comes a point when the app is done, and you're adding features just for the sake of it. What use is subscription pricing then?
That's a valid question. And my answer is: I don't know if it's any good at that point. Let's see when we get there. In the meanwhile developers are paid wages and I get use and value out of their software, so in the meanwhile paying makes sense.
And I think that really sums up one of the difference in thinking here - saving up for an unknown future is beneficial, but when it comes to software and services I'd rather pay now for use and value now (with my particular expectations in mind, of course - such as future access to my own content), than try to predict which app or application is a good investment.