> Construct 3 is what we need to have hope for in future terms.
> ...
> Is C2 gonna change into the engine that you envision? Probably not, because Scirra is now more focused on C3 and perhaps that will be the engine that you envision.
> ...
> I think that Construct 3 is what will move Scirra forward.
>
> and we are very anxiously awaiting C3.
>
You both know that C3 is planning on using the exact same HTML5 export/runtime as C2 right?
> BTW the stated goal of C3 is to rebuild the editor and keep the same runtime, so this is not really the kind of thing we intend to change anyway in the scope of that project.
>
Source: will-the-top-level-design-be-removed-in-c3_p980758?#p980758
The only thing you can actually anticipate for is devices, browsers, and NodeJS to all catch up to the "standard" of HTML5...which is also the same dragon C2 users have been chasing since the first betas came out in 2011.
Granted, it's getting better slowly but surely. However, if you're making and releasing games *now* you would hope that your game works the same across all of your customers devices right? And it doesn't, it's all over the map with desktop export, mobile, and even web browsers still have major differences between them (Chrome goes through cycles of breaking-changes and patches, etc).
Don't forget that you are a customer of Construct 2 meaning you are also buying a product which is supposed to do what it says on the box, so when it tells you that you can export to "Windows, Mac, and Linux" using a Node-Webkit wrapper ( https://www.scirra.com/construct2#multi ) and then your game fails to run on the "Mac and Linux" parts, it is not acceptable! and telling us to "just wait for it to improve/get fixed" is also not a valid response!
I don't care if it's Node-Webkit that is broken, I paid Scirra for a tool that they say will work on Mac and Linux, and it doesn't for my (commercial) game. It barely even runs the same/without glitches across my Steam customers' computers too, and they have hardware that might be way better than mine or the exact same specs, it's random and *my* customers do not accept "Please wait for approximately 2 years for NodeJS to improve the export by using the latest Chrome...which will also disable Steam Achievements until Greenworks is updated, and introduce random new bugs because Chrome was updated".
Ashley has done wonders with CC and C2, and has made an awesome tool for "learning game development" and "making small games for mobile and web" with a great editor and really cool way of visually coding games, but for Construct to really move forward into the status that the "more professional" game development tools have it needs a stronger export option. I don't care if that means exporting to a format that can be imported by other engines, but the native export to console and desktop is looking like the absolute minimum export options that commercial game devs need to grow. (And no, WiiU doesn't count, because it doesn't support WebGL).
Yeah, I kinda forgot about that. Thank you for reminding me.
With that reminder. Then what's wrong with adding in Native Exportation options? If it's a change of the editor, and not the entire, then shouldn't they be also working on Native Exports? I know it's a long process, since 
Ashley has stated it many times but if C3 is gonna take a long time to release, do you guys think that that's what they're working on?