Ashley You say a lot of reasonable stuff, but I still have my doubts that HTML5 will ever perform at the level of native apps on mobile devices.
1. Running a game through a browser just eats up more resources than it needs to. Does it not? If I'm running mobile safari on an iPad, is it not having to process the game PLUS the browser? It's eating up processing power that could be used by the game. The browser is the middle man.
2. Apple may *never* fully support HTML5, because Apple likes to dominate their corner of the market. Do you really think that Apple will enable webGL and continue improving HTML5 support if it could mean losing a ton of money from app developers going the HTML5 route and circumventing the app store?
I very much wish to eat my words and be totally wrong about everything, but it isn't looking good to me. I know you had to choose a direction and run with it, but I feel like you're defending HTML5 partly because it's what you went with. You even said yourself that there are lots of problems with browser support, etc... yet Scirra boasts that Construct 2 is a direct competitor to other game development tools that export natively. This just isn't true.
I don't think I'd have so much of a problem with Construct 2 if it was just advertised as an HTML5 game maker with a warning that it's not really meant for top end mobile games. Instead it's marketed as a replacement to native apps. Also I just think Construct 2 is so damn good... and I just want to create native games with it and get maximum potential from it. :( There's no possibility of hiring someone to work on the exporters on the side somehow? Not even if we kickstart it?