I've since calmed down from the initial sticker shock of C3, but still maintain it signals the end of Construct. Here's the issue:
Hobbyists - will pay for one year (maybe two) on a subscription basis. The novelty of making "apps for fun" wears off quickly for most.
Dev - At $149 per year for the right to monetize apps, it's a tough sell. The app market is about dead for 90% of indie developers and Google Play constantly sends out bots for issues such as outdated Cordova plug-ins etc. They also constantly change their terms for monetization and as a dev, I don't want to be beholden to keeping a C3 license just to possible "fix" apps that are flagged on GP in the future. $12 a month just to use C3 is too much. Most "new devs" (Constuct level) will never see $12 a month. My latest app created with Android Studio made 2c today - that's right 2c. It's not as easy as many think.
The beauty of C2 was that you already owned the license, so any issues could be worked out "eventually'. It's a shame becasue despite my criticism of C3, I had a lot of fun with C2.
I don't remember the same defensiveness of C2 as there is for C3, in itself, that's an indicator to me that the subscription platform may be being realized as a mistake.
My greatest advise (positive criticism) would be this:
Do what the users are trying to do in order to show that it can be done.
User want:
To make apps and steam games
To have in app purchases that work every time on every platform
To have ads that are easy to integrate and work great and have high eCPM
And to create great multiplayer games and experiences that can drive users to play with their friends
If Construct team can provide a clear example of those being done, it will be much easier for users to do it. (And many bugs will be worked out in the process as well.) Thanks Scirra Team.