Thanks a lot to everybody.... if i knew before these problems... i will not buy construct2....this is a very bloking development for me....but in any way i will try to work with it... hoping for an upgrade that fix all these problem...as soon as possible...
Those aren't even issues, at all.
1. Unlikely to change, as those wrappers tend to try and go for feature completeness (a browser with a simplified GUI/without the chrome, basically). I really don't see the problem though. It's not as if a 100MB game would be anything of particular specialty. It's rather common for games to require quite a bit of hard-disk space. Generally, space requirements will be more balanced the bigger the game gets, as most of the space will be taken by your own digital assets.
2. Publishing to mobile platforms is generally more involved, even for native apps. Using tools like Phonegap Build and CocoonJS is as easy as it could possibly get.
Thanks to the nature of open source and FOSS, you can do both.
https://github.com/rogerwang/node-webki ... master/src
PS: You might also want to take a look into compression. Before deploying any of my works (even the smallest application written in C ), I usually try to compress assets as far as I can without sacrificing quality. I also create installers for every OS. For Windows, I can recommend NSIS. It's free and quite a fun experience.