I read a lot of optimization info regarding Construct 2, however i could not find anything related to RAM usage, only CPU and GPU.

Your best bet on an Android device would be to use an app. Sadly I cannot post URLs

My suggestion is to compare the Construct 2 memory number with those in a test project while using a few scenarios. You might find that the objects not on the screen might not be loaded into the RAM, thus your wardrobe must display as few sprites per page as possible to make it RAM-efficient.

Here's a snippet on how to create a log file with RAM usage in Android:

[quote:oub6smek]How to get a heap dump

I created the heap dump using the emulator.

I created a new avd for the 1.5 preview:

android create avd -n test -t 2
emulator -avd test[/code:oub6smek]
Then you can logon to the emulated phone and make sure that the /data/misc directory is writable :
[code:oub6smek]adb shell
chmod 777 /data/misc
exit
[/code:oub6smek]
Heap dumps are actually created by sending the process a SIGUSR1 (-10) signal.
[code:oub6smek]adb shell ps[/code:oub6smek]
check for the pid of your application
[code:oub6smek]adb shell kill -10 pid[/code:oub6smek]
You can check with
[code:oub6smek]adb shell logcat[/code:oub6smek]
whether it works. You should see something like:
[code:oub6smek]I/dalvikvm( ): threadid=7: reacting to signal 10 I/dalvikvm( ): SIGUSR1 forcing GC and HPROF dump I/dalvikvm( ): hprof: dumping VM heap to "/data/misc/heap-dump-tm- pid.hprof-hptemp". I/dalvikvm( ): hprof: dumping heap strings to "/data/misc/heap-dump-tm124026 3144-pid.hprof". I/dalvikvm( ): hprof: heap dump completed, temp file removed D/dalvikvm( ): GC freed 1292 objects / 92440 bytes in 11 sec D/dalvikvm( ): GC freed 215 objects / 9400 bytes in 963ms[/code:oub6smek]
now you can copy the heap dump from the (emulated) phone to the Desktop machine:
[code:oub6smek]adb pull /data/misc/heap-dump-tm-pid.hprof address.hprof[/code:oub6smek]
Now the file you will get does not conform to the "standard" Sun .hprof format but is written in Dalvik's own format and you need to convert it:
[code:oub6smek]hprof-conv heap-dump-tm-pid.hprof 4mat.hprof[/code:oub6smek]
Now you can use the Eclipse Memory analyzer to analyze the memory usage of your application.
Good luck!

Use emulators, make a test project with a lot more sprites and try to reach the maximum RAM for the low-end emulated device (which is usually 512MB). Once you reach by whatever means possible the 512 in Construct, export it and emulate it; see how it goes.