{"id":1521,"date":"2015-09-28T13:05:47","date_gmt":"2015-09-28T11:05:47","guid":{"rendered":"http:\/\/www.aymericlamboley.fr\/blog\/?p=1521"},"modified":"2015-10-02T17:46:49","modified_gmt":"2015-10-02T15:46:49","slug":"a-call-to-the-haxe-community","status":"publish","type":"post","link":"http:\/\/www.aymericlamboley.fr\/blog\/a-call-to-the-haxe-community\/","title":{"rendered":"A call to the Haxe community"},"content":{"rendered":"

This a blog post version of my post<\/a> on the Haxe forum which didn’t catch enough attention I think. Native Extensions are crucial for game development.<\/em><\/p>\n

Update: Kha & OpenFL, for example, have their own IAP extensions because of the different engine architecture. The blog post mentionned share some thoughts on Native Extensions, in fact… but nothing concrete is going on at the moment, no repository shared. Finally the native code should be the same, but the wrapper around the extension can change depending the engine. A native extension should have different building scripts depending the engine targeted, but the same native & Haxe codes. I hope we’ll see examples in the near future.<\/em><\/p>\n

We made recently several HTML5 games (Canvas\/WebGL) that were also delivered as an app thanks to CocoonJS<\/a> which deliver better performances than Phonegap\/Cordova. But the journey wasn’t easy: no obb support on Android, push notification certificate needed for iOS, a custom analytics library didn’t work on Android but worked fine on iOS. It’s simple if you deliver your game with CocoonJS you don’t have any control on the packing solution and so the whole process could be a nightmare. Recently CocoonJS has updated its portal and finally announced pricing<\/a>, no way! It’s time to reconsider some plan…
\nUnity WebGL is getting better, but still not ready to deliver properly WebGL browser<\/strong> mobile game. So it’s definitely time to focus (again) on Haxe<\/a>!
\n<\/p>\n

There are a tons of awesome Haxe frameworks\/libraries nowadays : OpenFL<\/a>, NME<\/a>, Luxe<\/a>, Heaps<\/a>, Kha<\/a>… pick the one you want to make your mobile game! But each time I try a new “system” for mobile game I’m looking its ecosystem. Making a mobile game nowadays, is not only pushing pixels on screens, it’s also having access to native services like In App Purchase, Push Notifications, Facebook Connect… and many of them shouldn’t affect if you’re using OpenFL or Luxe…<\/p>\n

I see engine offering their own solutions like Kha’s IAP<\/a> or OpenFL’s IAP<\/a>. But is there any reason why Kha created its own native extension?<\/p>\n

Since native extensions should be engine independant it could be something managed via the Haxe Foundation! I was disappointed when I read the post on Sharing between frameworks (Nme \/ OpenFl \/ Kha \/ GameDuell \/ Heaps \/ Snow \/ YourGreatFramework )<\/a>, nothing on Native Extensions!!<\/p>\n

Making native extension is a complex task and require lots of works to be fully tested and updated (I made several for AIR), things like In App Purchase are critical in an application…<\/p>\n

Is it something which could be managed by the Haxe Foundation? Or at least, be in one place? At the moment, it makes Haxe ecosystem feels way weaker than AIR’s one (and so hard to convince clients but also developers!) due to awesome ANEs developers like Distriqt<\/a> & Milkman<\/a> or also Unity thanks to Prime31 plugins<\/a>. It would benefit to many developers. They could be free & open sourced available in one place, or even managed by a commercial company with pricing… at the moment Flambe<\/a> sounds like the best way to go thanks to the AIR ecosystem which sounds more complete.<\/p>\n

And you, what’s your current position concerning Haxe Native Extensions?<\/p>\n","protected":false},"excerpt":{"rendered":"

This a blog post version of my post on the Haxe forum which didn’t catch enough attention I think. Native Extensions are crucial for game development. Update: Kha & OpenFL, for example, have their own IAP extensions because of the different engine architecture. The blog post mentionned share some thoughts on Native Extensions, in fact… … Continue reading A call to the Haxe community<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[70],"tags":[71],"_links":{"self":[{"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/posts\/1521"}],"collection":[{"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/comments?post=1521"}],"version-history":[{"count":11,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/posts\/1521\/revisions"}],"predecessor-version":[{"id":1532,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/posts\/1521\/revisions\/1532"}],"wp:attachment":[{"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/media?parent=1521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/categories?post=1521"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.aymericlamboley.fr\/blog\/wp-json\/wp\/v2\/tags?post=1521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}