Vaillant wrote:I do have some concerns regarding the plugin developers. I would be very disappointed if this new model is the reason that developers would leave the community and the fantastic plugins they make and maintain would be lost. So Matt and Jay, give them some love (discount?). Without the plugin developers and the fantastic community, Indigo for me would lose it’s top rating.
Yep, we definitely want to keep the developers happy since they are an integral part of our success.
IndigoSam wrote:I don't think this is a subscription model in the same sense as the other vendors in the software industry. The blog states it is an update subscription, i.e. you pay ahead for any updates for a year.
If I rented Adobe Photoshop for whatever it is (£10/month?) as soon as I stop the rental payments I would lose Photoshop. That isn't the case here, as soon as I stop paying the Indigo update payment I would still have Indigo.
Exactly. Given the quantity of complaints after the first day or so, it's pretty clear to us that the majority of the negative reactions came from people that didn't actually read the description of how the program works. They just assumed that it was the same model as Adobe, which it very clearly is not.
petematheson wrote:I'd also suggest communication should be better improved with a proper roadmap that is updated on a monthly basis.
We just want to set some expectations here because we've heard this a couple of times. Like all software companies, our roadmap is private. There are very few (if any) software companies that publish a roadmap to consumers - that always ends up hurting much more than helping because it limits flexibility in responding to new and changing priorities and it requires non-trivial management time (which takes away from development/qa time in a tiny company like us). SLA's for new features/functionality also doesn't exist except in the high-end enterprise software space (and even then it's generally for reacting to bugs rather than new features) - it's not something you see in the consumer software space. Both of us are veterans of the software industry on both sides (enterprise and consumer) and understand well all the implications.
Seeing a roadmap is secondary to the real problem: new device support and other new features take too long to get into the hands of customers. The new model is meant to alleviate that problem.
petematheson wrote:You could even move to a voting system to get an idea of where the community wants the development to focus on.
We already have a really good idea of what customers' priorities are - but remember that there are strategic priorities as well that are not necessarily something we communicate beforehand.
petematheson wrote: Integration with IFTTT would be a huge bonus and I feel should be quite a high priority, as that would bridge the gap between most of the newest technology that doesn't currently have an Indigo Plugin.
Unfortunately,
that's not up to us since they have to build the channel.
Redrocker wrote:I, as I'm sure many more here, will be watching closely. I won't repeat what has been already stated. But there are features that seem to be lacking, that for a long time user, seem to be no brainers, for a product as "mature" as Indigo!
One man's
no brainer is another man's
I can't believe anyone would use that feature. Perspective and context are everything when determining priorities. While we don't always get them right (i.e. not updating Indigo Touch sooner), I think we do a pretty good job overall prioritizing new features/functionality. The update subscriptions are an attempt to get these new features out to customers faster.