Thanks for the great answer!
If I have other question it would be... what is the most intense Construct 2 project that's been exported to mobile devices? Like with the most characters, animations, rules etc that are in one single scene?
I would love to see that to see if my future projects can run on it as I wanna make money on the App store with some pretty big games. :)
I don't know if loot pursuit is the most intense project at any one point, as I'm optimizing as much as possible, however it is a substantial project. The main problem right now is memory management, which Ludei has said they've started working on. It was running fine on my iPhone 4S until I started using more ram than the device has (still runs fine on my pad 3 which has twice the ram), hopefully ludei's implementation will fix that problem (it sounds like it will).
> Lovelocke64, actually by now, with Node-Webkit, C2 is almost as powerful as CC for desktop games, and it has so many benefits like active community, constant updates, more features, etc.
Not trying to start anything here, but "almost" doesn't "equal". For my purposes, Node-Webkit is tricky to get video playback working, and for (enough) other users, they experience glitches ranging from unpredictable performance to audio glitches.
I'm sure the same errors can creep up in Construct Classic, but nothing beats native export like native export.
Besides, for our OP's requirements, iOS/Android development, whew. The Android development side of exporting requires even more troubleshooting to get "right". Another issue of the long-winded talks on "native export" support that pops up weekly on the forums.
Although I haven't tried video in C2 yet, the lack of complaints about it makes me think that video playback was worse in CC, as in CC there was virtually no control over the video, it always has a control bar, and I seem to recall I couldn't even destroy the object. It was basically useless. :(
CC export wasn't perfect either, players of CC games would sometimes report crashes. Besides, for every thing CC does better, which isn't much, there are a bunch more things that C2 does better.
Also, I apologize if I'm misunderstanding, but it sounds like you're implying native export to android would make things easier - but from the developers I've heard from and talk to, native development sounds even worse! Hundreds, if not thousands of devices running tons of various modified versions of android with different hardware specs that often don't even support the features they claim to support. Native export is not a silver bullet that is always better at everything. It's no wonder scirra's competitors are taking so long to update if they're trying to make a native android exporter by themselves.