Thanks guys, this does point me closer to doing an update rather than a new item. To be honest, I don’t see either option giving me increased sales, as it’s held steady since day 1. It would of course be preferable to keep the confidence of buyers.
It’s a change that will put out an entirely new API . I would assume that if someone wants it badly enough, they would prefer to update their existing installation rather than purchase a new item. Normally I would keep the old API integrated as deprecated functions, but being JavaScript I don’t want the file to get any larger than it already is.
Hey guys!
I’m in a bit of a pickle. One of my items is in need of an update, and I’ve made some promises to people who have purchased it that they would see some of these changes.
However, as I’m working on this it’s clear that it’s an enormous update. So enormous, in fact, that it will end up breaking existing installations. It’s built entirely in JavaScript with a lot of user-defined options, so I can’t do any kind of auto-update for them.
What I’m trying to decide is, should I make this an entirely new item? Or should I put out an update with the changes and just put an explanation that they’re going to need to basically change everything around? I’m leaning towards the latter, as I don’t want to come off as going back on my promises, but I also don’t like the idea of forcing everyone to change their setups.
Any thoughts? I figure it’s best to get the opinion of buyers and other authors who have gone through the same thing.
