0 Favourites

Why Crosswalk export is called Android?

  • It's something that i've been wondering. Why Crosswalk export is called Android and Cocoonjs is not? Why node-webkit in not called exe? I think that calling Crosswalk export Android export is confusing. I've seen some users that expected and apk and not a folder to be processed through intel xdk

    just saying.

  • Crosswalk does only android, while CocoonJS does Android and iOS

    also Node Webkit exports for Windows, Linux and MacOS, so .exe will not be accurate

  • Crosswalk does only android, while CocoonJS does Android and iOS

    also Node Webkit exports for Windows, Linux and MacOS, so .exe will not be accurate

    <img src="smileys/smiley9.gif" border="0" align="middle" /><img src="smileys/smiley9.gif" border="0" align="middle" />

    Thanks for your answer, i see it more crearly now. You're totally right, i'll eat my words....but, IMHO, with this name it looks like C2 has a direct android export option..

  • Agreed, I like to think it was a way for scirra to say "Don't use CocoonJS as we don't want to support it anymore", but I'm going into personal opinion

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • Sadly CocoonJS is still the only viable iOS export since its got monetization features.

  • The reason Crosswalk is called Android for export is because Ashley believes that Crosswalk finally makes all the requirements for what should be Android export.

    I however disagree and believe that calling XWalk the Android export is jumping the gun. First Crosswalk is great, but it's slower than CJS so far. It does finally solve many weak points of CJS however and that's why it's good.

    What for me I think the reason XWalk should not be called Android. Because Ashley right now could use C2 to actually make a real signed APK compile from C2; just like NodeWebkit. There is with some technical know how to even use XWalk for anything. Considering that we need to upload our assets to Intel XWalk cloud this is not really a long term viable production toolset. I have a game that when on release will be about 200MB. And after working with others in a team I can honestly say that modified assets come in far too often to have to constantly manage XWalk way of clouding of the data.

    Ashley should dump XWalk and just make everyone install the JRE & ADK and just let us compile with out. Until then I don't think XWalk deserves to have the label Android.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)
Similar Topics Posts Views Last Post
Unread hot topic
1,257 133,578
vampire6's avatar
vampire6
Unread sticky
763 305,714
asikanddestroy's avatar
asikanddestroy
Unread hot topic
0 Favourites
New Android Export Experiences
494 67,280
jabk's avatar
jabk