bertie Booster: Eisenhan is right. The runtime is part of the APK. That is why it is 17MB.
>
> > I would have concerns about publishing software that relied on a wrapper that could be unilateraly updated/changed at any time after the game is published. No offence to Intel but you want to do all your testing & debugging before launch not every time crosswalk is updated.
>
> Why does a Crosswalk update affect you that happens after your APK went onto the Google store?
>
> It's not a "live" connection.
Sorry we've crossed wires here I was referring to a possible scenario if the methodology discussed in the post previous to mine was adopted
—
I understand that it's not "Live" at the moment and trust me I've looked at that 17MB very closely as the APK approaches 50MB.
My concern is that a game I write and debug/test using say Crosswalk 2.2.4 could be installed work and then break when the customer is required to install say Crosswalk 2.6.1 a few games later. Anyone who Flash Dev'd with AIR will know what can happen when the AIR runtime is updated although to be fair the problems were predominantly in the early days.
If Intel are going to go the way of a one (install) to many (apps) option I do hope there is some way of signing an app to only use verified versions incorporated.