Possible solution for subscription problem, What you think?

To the people that only want the C3 they can purchase one time by $99 and use it always, they will have lifetime bug fixes but only 1 year of free updates/improvements.

So people will enjoy the new C3 version with one year of great upgrades for only one payment. Some people not needs much more, like people is doing games only for fun, as hobby or even sell some small games or whatever.(That well, they can still doing that with C2).

In case there is some features and improvements that are added that gives to a developer a good reason to update the product they can decide to pay again $99 and enjoy of all the previous updates until now and 1 year forward.

With this people with non-profit/hobby,etc... expectations that want the new version can afford that, and for the more advanced developers that needs the last updates they can pay the subscription each year to be updated.

What you think? is possible Tom Ashley ?

Interesting, Scirra should think about this solution

Or, provide 2 different order options.

1. Pay $99 / year as per the currently proposed model.

OR

2. Pay a one time fee for the same unlimited version as above but add an additional charge per export.

Also perhaps the fees could be decreased if the cloud based services were offered separately. Those who want them can pay an extra fee for access.

matriax I agree, I posted a very similar idea here:

+1 to OP

• & at discount to existing owners, and at GREATER discount to business license owners, if personal/business licenses get scrapped

• & for a lower fee to people who don't want to make use of the web IDE/cloud functionality

To the people that only want the C3 they can purchase one time by $99 and use it always, they will have lifetime bug fixes but only 1 year of free updates/improvements.

So people will enjoy the new C3 version with one year of great upgrades for only one payment. Some people not needs much more, like people is doing games only for fun, as hobby or even sell some small games or whatever.(That well, they can still doing that with C2).

In case there is some features and improvements that are added that gives to a developer a good reason to update the product they can decide to pay again $99 and enjoy of all the previous updates until now and 1 year forward.

With this people with non-profit/hobby,etc... expectations that want the new version can afford that, and for the more advanced developers that needs the last updates they can pay the subscription each year to be updated.

What you think? is possible Tom Ashley ?

I except there will have no "Closed. Won't fix."

That's impossible. You can't give people bug fixes without the new updates, unless for each revision, you maintain a separate branch of the engine.

There's an idea knocking about in pro audio circles of "Rent to own" whereby you pay a monthly fee which can be cancelled at any time, but once you've payed off the price of the product you own it. I actually think this is an appealing system because this kind of software isn't cheap, usually starting at a few hundred $ a pop. This way though the devs get a steady stream of income coming in for ongoing development costs and users can slowly pay off a piece of professional software to eventually own. Its kind of meeting developers and users in the middle and I think its far less obnoxious than pure subscription models. Its something to think about anyway, as subscription models are universally maligned by users.

There's no problem with the subscription model. Let me explain.

1. A subscription model will ensure that the devs are getting a steady income to continue develop their product, provide support andmaybe even afford to hire some people to add some of the most requested features. Is this a bad thing?

2. They could have planned it differently by already planning for a C4 or C3.5, next year where people would have to pay again, but it's not good to keep and maintain too many products. So going with a subscription model for C3 will ensure that people people who are using it, are getting the latest updates, bug fixes, for some time onwards, so they can focus on C3, leave C2 behind them and only provide minor fixes and tweaks for older products.

3. It's not corporate greed, it's just a business strategy so that they can continue to provide a good product, and good support, and continue the development. Would you be happy if your boss told you he won't pay your salary next month because he already payed you once. Maybe some people has used C2 for years and years, but are still expecting support and bug fixes and features.

4. Although i think the subscription model would work very well, if they want to cater for a lot of different target groups. Maybe they could lower the price a bit later on for the core features (for hobbyists), and add optional packages for people wanting native exporters, mobile development, kongregate package, 3d editor, team oriented features, monetization package. I would happily pay and support yearly, for ALL they features I want, and I don't have to pay for the features I don't want or use, but If I'm a hobbyist maybe the core features is enough.

I don't mind paying for things i like and especially for support, as C2 clearly stand out as one of the best support I ever had. I've posted several bugs and feature requests, that got fixed in the next updates.

That's impossible. You can't give people bug fixes without the new updates, unless for each revision, you maintain a separate branch of the engine.

You would still get the full updates but your version of the program would be feature locked.

I chatted to Ashley about this, and it's not an option as the previous poster mentioned it would be a maintenance nightmare. There would be loads of branches to update and maintain and ultimately would slow progress down of Construct 3.

I chatted to Ashley about this, and it's not an option as the previous poster mentioned it would be a maintenance nightmare. There would be loads of branches to update and maintain and ultimately would slow progress down of Construct 3.

Maybe I'm not understanding (and granted, you're going to do what you're going to do, of course, so this probably won't change anything) but it seems to me you could just have the 1 branch, sign into your account to use the editor (even in offline mode), and your account would be assigned an access level ("bug fixes class" or "new features class") and depending on the access class certain features would be greyed out.

Well.. I suppose assigning features to paid up user or not paid up user would take some extra work.

Edit: I mean, doesn't the free version of C2 already have the latest updates but with certain features restricted?

Or.. well, I suppose they're all there but it just has output limitations. I suppose it would take more work on restricting features but that seems to illustrate the possibility.

Maybe something inbetween?

Free version - Limited features for tryout, learning, experimentation.

Pay once or reduced monthly payment for the core features. (for hobbyists) You will get updates and bug fixes, but still locked out from some features. A one time fee is quite hefty for some people so monthly is still a good option.

Monthly payment for extended support package. (Email, phone support, Remote assistance?)

Monthly/Yearly Packages for other advanced features like. (Native exporter, Team tools, Monetization, cloud storage etc etc, based on your needs, .)

Business Package - All inclusive monthly/yearly payment with a discount for multiple seats/licences?

Maybe something like that would work well?

At least that would cater for both hobbyists and business oriented crowd.

Tom At least if somebody buys the C3, he can still code with the last online version now offline where the subscription ended?

Is something that not was clear, i mean, if i pay $300 for 3 years... after cancel the subscription, i can't code in C3? or i still will can develop in C3 with the exports,etc... as normal but without no more Bug Fixes/Features?

I chatted to Ashley about this, and it's not an option as the previous poster mentioned it would be a maintenance nightmare. There would be loads of branches to update and maintain and ultimately would slow progress down of Construct 3.

I think the best way would be what matriax suggested:

Is something that not was clear, i mean, if i pay $300 for 3 years... after cancel the subscription, i can't code in C3? or i still will can develop in C3 with the exports,etc... as normal but without no more Bug Fixes/Features?

I also think that people who cancel their subscription should be able to keep the product for use. But they shouldn't be able to make money from a project that has been exported without a subscription. And they wouldn't get any updates and fixes. That way you'd only have to support the newest version of the engine which the subscribed users get instantly.