yeah, people are getting pretty passionate about it, and unfortunately as much as i and some construct loyalists are fine with it, and just eager to get them on their way financially, the roughly 65 percent who approve is not very promising. I think honestly it's just hard for people to put aside the fact that it's not complete at the moment. Until it is, you're going to have to be sustained on the community who already trusts it will eventually get there.
with a complete product, there will be less resistance, but i think it'll be important to point out how many +1 versions competitors have, most have more than 1 every two years.
just thought of this.
maybe you should just have a set group of features that construct 3 will have, still do incremental updates, but when it reaches that level, people who have paid for the subscription fee will still get it even if it's called c3
it won't even be a subscription, it'll be a future proofing promise. its the free update guarantee, which extends to +1 versions as well.
that'll feel better for most. which i think is the main problem, is this is a different business model, and the words just don't sit right with alot of people. which may seem insignificant, but it's not...it's pretty much everything when it comes to selling something. to them it feels almost like a product rental, and not only that, but a rental of something incomplete with no clear idea of what they'll have when the rental expires.
promise what 2.0 will have. at that point, decide the features of 3.0, increment the updates over the next months or years, and deliver, and I think people will be happier.
maybe even at this early stage, it might be a good idea to compile a list of promised features for 2.0, to get some more early adopters, as well