Hi 
Ashley and 
Tom
I have a question about memory use - it would be really cool to hear from the founders of Construct, to help put me on the right track.
I don't always make the conventional types of games, made with Construct (e.g. platformers, shooters, physics).
Here is one of my examples - http://www.ninjadoodle.com/clickplaytime-6http://www.ninjadoodle.com/clickplaytime-6
Since one of my goals is to make fullscreen browser games (as well as mobile playable), I'm trying to find a good balance between high resolution and memory use.
Since Construct doesn't support containers (in the sense that you put objects inside a container, then tween, squash and stretch as if it were one object), I have to export animation sequences for some of my levels.
My sprites can often be very large, as they are the main focus of the puzzle/level. I've tried most of the tips and tricks I could think of, but without compromising my designs, I'm finding it very hard to stick to the 100mb recommendation for memory use.
I see that this article was written some time ago, and was wondering whether you might have a recommendation for a 'safe' memory use limit that I should stick to, as a middle ground between memory use and the types of levels I want to create.
Thank you very much in advance for taking the time out to read this post