I am sure they'll focus on .exe exporter as soon as they get major roadblocks out of the way - that being the fact they're still studying. Until then, HTML5 seems like the "cheap" option to build Construct 2 on - it is much easier and faster to develop than OpenGL windows app.
(I wonder - could the Construct 0.x runtime be extracted for use with Construct 2? I know it is DirectX and all, but hey, it has effects, .exe etc.)
Anyway, as the license is concerned, I had planned to buy the better license to help motivate the project. I've got a suggestion however - what about an one-year license? That'd be attractive to part-time users.
Another suggestion - the demo should be latest stable release, while license should grant access to development builds. That way you'll get people who want in on the newest features to buy a license (especially if it is going to take a month or more between stable releases).
Now, there is one concern - compatibility between projects, made in different versions of Construct 2. One could be made in stable release demo, other in nightly build; obviously we can't expect that to go very smoothly for team projects.
Now, a question since I just mentioned team projects - how would you approach team licenses? One for all copies of Construct 2 running on different computers? Or will each instance require its own license? The obvious choice is to allow several Construct 2 instances with one license, since the other option sounds too harsh for people with laptop, desktop PC, mac and smart fridge.
Well then, I should be working now. Excuse me.