3 ms·
I am employed by one of the companies discussed, and while I was on the fence about subscriptions originally, I've come to change my opinion. While not ideal f
by diggum 9y ago
I am employed by one of the companies discussed, and while I was on the fence about subscriptions originally, I've come to change my opinion. While not ideal for a subset of users who might use only one or two applications, it is less expensive for the majority of users. It's also lowered the barrier of entry significantly, which has invited a lot of new users, reduced piracy, and encouraged use and exploration of applications they might have avoided in the past.
From the development side of the business, the more frequent release cycle has allowed the product teams to be much more responsive. Under the old model, with major updates every 18-24 months, I might receive a feature request which is implemented in a few weeks, but which the user doesn't have access to for a year or more. This was hugely frustrating as we want to make features and products our customers want to use, and to have it ready and waiting for so long was not a great experience for anyone. Now, we can have that feature in users hands in weeks or months.
I don't understand this idea that there will be reduced incentive to release updates under a subscription or membership model. If anything, frequency and responsiveness feels more important than before, and I don't know of anyone here who feels differently.
edit: I was more on the fence about subscriptions than unsupportive. It was a drastic change that required either gradual transition or a rip-off-the-bandaid approach.
- pspeter3 9y agoThis is what I thought would be the natural outcome. I'm glad to hear it's working out for you!