juannn91 yea we read this but they mean when C2 is running a game in a normal browser.
In our extensive testing (I'm working with my partner who's a capable HTML5 developer and experience with OSX / Android) he could see very clearly when the game was being loaded using I believe XDK or maybe Ejecta, that EVERYTHING was loading into ram at the start of the app, not scene by scene..
This is unfortunately probably something that C2 has no control over, once its wrapped in another container system, memory management gets lost in the process.
Our 2nd project is being made for mobile and going much smoother, although I sill have to watch out for large audio files causing problems. Asside from that our 2nd project which has considerably less content and content optimized for mobile (keeping things in powers of 2 and starting with a 720p screen instead of 1080p)
So yea our next move is to simply go back and scale down all of the art considerably. this will cause some issues with visual quality, but we're optimistic that on an ipad it will be less noticable than if it were on a 26" monitor.