Intelrobert: First, thank you so much for your open communication with the community. I think we all here appreciate that very much.
So I tested the new exporter as well but I noticed 3 things:
1. My Spriter animations aren't working. They work perfectly fine in Chrome, Node-Webkit and CocoonJS. I use the most up to date version of spriter/ the plugin and all my animations are running on ".scon"
2. My game uses even more memory ( RAM ) than it did with CocoonJS. In Construct 2, testing with Chrome, it says 12 MB. With CocoonJS I get 80-100 MB, with Crosswalk I get 140 MB. Which is very surprising. I don't know if I do something wrong here, since I though Crosswalk handles memory well.
3. Playing the game feels a bit "wobbly", like playing a website hosted HTML 5 game on your phone. CocoonJS feels more natural and like a real app here. The framerate was OK with Crosswalk. I don't know how to find out the exact FPS, but It felt mostly fluent ( with CocoonJS the game runs with 60 FPS). Next the CPU usage was higher than with CocoonJS: Crosswalk 5% CPU, Cocoonjs: 1-3% CPU.
All in all, I trust that Intel will make Crosswalk work properly. I am just skeptic, if they will manage to capture the 100% native app feel eventually.
Did anyone make similar experiences with memory management and Spriter animations?