Make sure you read the manual and get to know what Construct 2 is capable of. Which is a lot. You've actually gotten started with Construct 2 at a pretty good time. HTML5 games take quite a bit of optimizing for mobile devices but phones have become stronger since the release of Construct 2. Then there's the crowd of people saying: "WE WANT NATIVE EXPORTERS!!!!!". Anyways, if you want to develop for Android or iOS check out Intel XDK (I still haven't used it yet but apparently is the easiest to use with C2) or Cocoon.IO (Which I use, and it's awesome because of Canvas+).

Nice job! Solid visuals and gameplay.

May I just recommend one thing with your games though. Try doing outside the box concepts. This game and the other game you've made are good but I think a lot of players look for outrageous things in game as well.

> Have you tried using the Cocoon.IO? Canvas+ performance is quite something.

>

Do you have any Android mobile app on Google Play made with C2 and wrapped with Cocoon.IO?

No, I do not. Yeah I know, "Then why are you even recommending Cocoon.IO?". I just think that gaelsev will have a solution to his performance problems via Canvas+. Testing with Cocoon.IO is great! So I can say that I've done that. Although, the pricing for the plans is quite insane.

Hello,

I looked to use Cocoon.IO but we must quibble to build .APK and wait a long time to compile (in freemium). I don't have the courage to look more with Cocoon.IO lol.

What's exactly the problem with Cocoon.IO? I can't seem understand what's the problem? It's quite easy to use, if you need help, just ask.

> I have no issues using Crosswalk+IntelXDK on mobile exports. I would suggest following the tutorials about code optimization and testing the game on each device from development start. At the moment I tested my APKs from 4.1 to 4.4 and they runs pretty fine.

>

Hi friend,

I already followed optimization tutos, but is not the problem sadly.

Dynamic games with a constant 55-60 FPS is not possible on mobile for the moment with C2/intel XDK.

If you want i can show you my game in PM.

Best regards,

Have you tried using the Cocoon.IO? Canvas+ performance is quite something.

I noticed while testing a new mechanic within my game, is that when I've got many objects time-scale set to quite a low scale and they're all moving slowly, that performance actually goes down. Why is this? The objects are moving slower, shouldn't that make the performance better?

btw, this is on mobile.

I'm probably gonna get a good reason. Can't wait!

Is the main problem that everyone has issue with the cost of the splash screen removal? I mean, sure it's ridiculous but is there any other bad thing about it? The paid plans aren't really necessary unless your game is really big or you just want have more than 2 projects in the cloud at a time.

It's really good for your first app. Congratulations.

Only thing I recommend now is to make a more complex game, haha.

What I've got is the player and enemies moving towards the player. For player movement, I want to add a node system. This node system would have the player place about 10 nodes for the ship to move to, only after all ten nodes have been placed onto the layout. I'm having trouble on how to spawn the nodes in order and how would I make the player's ship move to the direction each node in order.

Node 1 is placed on one tap, then the next tap places Node 2 and so on. Once all nodes have been placed, the player's ship moves to the nodes in order.

Here's where I'm stuck (It's painfully bad):

https://www.dropbox.com/s/mitg7usedgu88 ... .capx?dl=0

You will need Boids Flocking behavior in order to look at the CAPX:

behaviour-boids-flocking_t77775

What is the difference to use Intel XDK or cocoonjs?

CocoonJS has better performance via Canvas+ but Intel XDK has better compatibility with adding ads, IAP, and is basically smoother to work with. There's also Cocoon.IO, which is Ludei's new Compiling service and it's still in prototyping but C2 games can also be exported using that as well.

Try out CocoonJS

But if we use Tiny PNG, that would still decrease the size of our game. Right?