Gianmichele

someone would download Android game,

see jittering in Crosswalk,

and then what?

I have downloaded "Airscape" demo long time ago, and it was jittering too

soo maybe it would be shoot in the foot

— Sisyphus

one week ago I have compiled my APK using CocoonJS 2.1.1 + plugin for C2

and I use 'Webstorage' plugin too - and everything is working fine

Softloulou

additionally even in much more smooth Internet Explorer I see seams in TileMaps (even in seamless mode).

Paradoxally when CocoonJS was deprecated by Scirra,

ludei started doing really good job

And in case of support CocoonJS is now much more reliable than Chromium/Google.

So good luck and keep it on

Everything should be fine in 2015 or beyond.

You could setup pause in general event sheet, and then triggers it when neccessary

i.e.

on touched "pause button"

-- set time scale to 0

-- system spawn object 'white box' on layout...

-- system spawn object 'home button' on layout...

-- system spawn object 'replay button' on layout...

-- system sprawn object 'play button' on layout...

on touched "play" button

-- "white box" destroy

-- "home button" destroy

-- "replay button" destroy

-- set time scale to 1

About question no. 2

Android:

You can compile your app using Crosswalk = you can use native AdMob ads, but your game will jitter

You can compile your app using CocoonJS = game will not jitter (or jitter much less) but you can't use native AdMob, only MoPub (so you will earn 70*% less due to low fill rates and low eCPM)

iOS:

You can compile your app using CocoonJS and get amazing perfomance, however CocoonJS still uses MoPub, so you will earn 70%* less on ads (comparing to native ads)

So we are still waiting for ludei to implement native AdMob ads

and we are still waiting for not jittering Crosswalk IntelRobert

Of course you can still make super advanced 1 screen game and compile it with Crosswalk, and hope that jittering won't be visible.

* - at least

russpuppy

gameplay 7/10

graphics - erhmmm

Softloulou Aphrodite

Gianmichele wrote about auto updating webview in Android 5.0:

Honestly I'm a really scared that an auto updating webview, more than nodewebkit, could break a perfectly working game without any action from the user (or even knowing it really).

Ashley replied:

Google already manage to do this without breaking the entire Internet, so I'm sure apps will be fine too.

***

so everything is fine...

Alatok

That's good idea. In my case I hope for native AdMob from ludei and meantime I will work on some simple app that could run well even on jittering Crosswalk.

Verily Construct 2 teaches us patience

Alatok

it seems that Unity etc. and all other engines with native exporters are 100% wrong

Ashley says also "Like I said, most projects which run in to trouble are either exceeding hardware limitations, or grossly inefficiently designed." which sounds really funny if you think about strong jittering / micro-stuttering issues. And the latest CAPX by Softloulou is the best example.

Alatok Softloulou

as much as I love Construct 2, I strongly disagree with Scirra's approach to exporters. The best example is Android: CocoonJS was deprecated and what alternative do we have? Jittering Crosswalk. It's just soo not professional, ehh. And it's always about waiting for better future.