Why Construct 3?

The conversation is 'Why Construct 3' hence the tittle.

The authoritarian approach has its positive sides, but ...

I dont see any notable addon creator, who confirmed that he will write for C3. So ... good conversation

Why do we have to wait for the future of C3? The future is now. Remaining with C2 is living in the past, a past which is already fading away. Despite the fact I also liked C2 very much and it is still on this laptop, I keep myself from using it.

C3 is the future and the only way to go. Do you really want the Scirra team dividing their resources between C2 and C3? I think their time is better spent on C3 because in that way they can give us new features much quicker and can concentrate to make many improvements.

Rex Rainbow made a lot of very usefull plugins for C2. Many people used them and he did a great job. When my understanding is correct, Rex Rainbow decided a time ago not to port his plugins to C3. I regret his decision very much but have to respect that. However, are we gonna put the future of C3 on the decision of one man? That is not a good idea in my opinion.

Also with C3, everybody of us can write his/her own plugin in JavaScript when necessary. I am sure other people will fill the places of those who left.

I see a very good and stable future for C3. One of my wishes is that in the future, we can use Construct also for developing administrational programs, the same way as now developing a game. When I first came accross Construct 2, I found it a revolutionairy method. To be honest, I was worried about the lifetime license because one time in the future it limits the revenue for the developers. I want the tools I use to have a stable future. Lifetime licenses are just the other way around. And when you do not agree with me about lifetime licenses, let me give you one question ;

When you create a popular program which took you years to develop and once you release it you know you have to maintain it for years. You have many users which start to ask new features. In the first years you get a lot of new users, however your sales start to degrade. You know you have to support your family but also your development team. You desperate need resources to support new developments and has to keep up with the competition. Still your revenue is degrading because everybody is using your lifetime license. Your users are very happy because they ask you and they receive what they want for free. However there comes a time your revenue will sink to such low limits, it is no longer worthwhile to sustain your wonderfull application. On that moment your application dies.

Now my question : how many of you offer lifetime licenses for the applications you develop? How many of you are working for free for your boss or your customers? I am sure this conclude the discussion about the subscription model.

There is indeed room for improvement in C3 and to be honest that need will remain for the future too. C3 is an excellent tool with very good customer support coming from the Scirra team and the community. We all have something unique here, both in development but also a friendly way of helping each other. There are a lot of tutorials which teach us how to use this remarkable tool.

Instead of keeping with C2 and threads like this one, why are we not combining our efforts to make constructive threads which helps us all?

For new or prospective users, reading threads like these, I advise you to try out the free C3 version. It is very limited, however you will get the chance to make your own conclusions. I saw threads like these showing up too much in the past and their only intent is push a personal frustration or disagreement onto the community. I rarely find them constructive.

Make some efforts, learn, fall and standup and above all believe in your idea. That is what development is all about because when it was easy, many more people would do it.

For your information, I am not connected with Scirra in any way but I am very good with bookkeeping. What you read in this reply is my personal opinion.

Chris

However, are we gonna put the future of C3 on the decision of one man? That is not a good idea in my opinion.

I would be more confident if the base package had more of these quality of life improvements built in, so that we had proper ongoing support from the actual developers.

In my many years as a TD who has used (and coded) for a myriad of different post-production DCCs (e.g. AE, Maya, LW, Nuke, etc), I've arrived at the opinion that regardless of how good or bad the base product is, the 3rd-party developers have always been a cornerstone of any real-world/professional situation.

The host app devs can't provide all the tools that their user base are using, and determining what are essential features are ultimately confusing; many are essential features, and only few are not. These features may just be small 'quality of life' features, or a 'I didn't know you could do this in this app!' kind of feature. The tools themselves are not point; it's the fact that you can't possibly expect the host app dev to come with that at the rate you're experiencing.

But I think the expectation -- explicit and implicit -- that *some* 3rd-party devs will inevitably fall by the wayside mis-judges their contribution to the product: there is the intangible value of their responsiveness of knowing what is needed in the real-world and implementing a solution. Users often talk about 3rd-party as 'tools' or 'plugins. It's not just about the plugins but the 3rd-party devs ongoing involvement that makes a difference. You won't get that level of nitty-gritty involvement from Scirra; you can't get that from any developer. (You can, however, wait in line until the feature you're pining for happens to get added.)

This is the reason why I saw Rex's leaving, whose reason was strictly due to the SDK, was really a pity.

The one thing that construct has against it, that i think scirra doesn't see, and it really is it's Achilles heel, is the asset management pipeline.

It's hard to hold one's breath on that one. After a few years in the forums, simply observing the kind of the features and improvements that have been implemented, then the C3 reveal, it's pretty clear to me that 'management' or 'pipeline' is just simply not quite the gripping concept in the Construct world as it is in other worlds. I think they'd have to bring in someone who has some serious experience in larger projects, using another app, in order to understand.

(E.g. I wrote a Sprite Manager for C2 -- a Python app -- for personal use to deal with a massive amount of animation sprites. I figured that I couldn't wait, and that there is no guarantee that any improvements in asset management will be relevant to me.)