Flax Project San Francisco trip to Game Closure
What did the Flax guys get up to at Game Closure?
Well after recovering from the jet lag of flying half way around the globe, Carl and I got down to familiarising ourselves with Game Closures SDK, and general development environment. Now do forgive me, but I’m going to be some what vague about all this; NDA’s and all. Though rightly so, some extremely ground breaking developments happening at Game Closure, that make their dev toolchain very unique. As the lead programmer of the Flax Engine, I found it quite interesting to study their SDK’s architecture. Its always nice to find almost identical algorithms or structures in some sections of the code. For me it helps validate my logical thought pattern about a problem when someone else writes very similar code to solve said problem. Even more interesting are the different approaches and structures people use to develop a game SDK.
So Carl and I went about almost stress testing the SDK (we didn’t know the SDK at all, we picked a random game and said, ok, lets do this in two days). Within two days we had put together a basic top down scrolling map shooter. It was about the third day when Michael came over to us, asking how the game was going and had we tried it on a device yet? I responded no, knowing all too well the pain it normally takes to get a HTML5 game working and performing well in a mobile device web-view. Michael pulled out his android phone, opened their Game Closure dev app and there on a list was the name of our game, one tap and bang, there was our game running! Not only that, but the performance was amazing; particularly for such a low end android mobile device. To be honest, I was quite puzzled by this black magic. Michael explained how their SDK and server development works in-conjunction, to compile HTML5 apps into native apps for all mobile platforms. So what we were seeing was our game as an almost native .apk installed game. I quickly changed some of the source code and asked him to refresh the app, and bang, there was the altered game.
These days the whole focus of game development, seems to be write it once, deploy on all platforms. Many frameworks and SDKs try to achieve this, and coming from a GWT background I’m very fimialar with this idea, of writing all the code in one language, both server and client, and then deploying to all platforms without the need to rewrite. I have experienced the problems that can come with it, and the general pot holes that slow developers down. Never before had I come across a solution that “just works”, and that was so natural to general HTML5 development. There is so much more that really blew me away; but I best stop there as I have signed an NDA.
For the remainder of our trip, we tried out various game genres and developed prototypes to further help us evaluate their game development stack. I’m quite pleased with how our trip worked out, it was a great success for both parties involved, Game Closure got an outsider’s view and evaluation of their development stack and we got a free plane ticket and Holiday to Silicon Valley, ha . Ah no, but on a more serious note, we got to be in an extremely motivated and passionate games development environment, which was a first for Carl and I previously working in more standard software development environments. Not only that, but working with such talented engineers was an great experience, I feel I was barely worthy to be among them.
So that was our trip to Silicon Valley, and we are now back in college catching up on what we missed. Though I must say a special thanks, for the support of our lecturers, who facilitated our absence and allowed academic value to be derived from our trip. Special thanks to Michael Carter for inviting us out, and to all the Game Closure crew for having us. Of course a big thanks to Tom, Marcus, Bridget and Jacob for their hospitality. We would also like to say a big thank Michael and Game Closure for offering to sponsor the Flax Project, which we kindly accepted. Most importantly, I must mention Teddy Cross, Game Closures current intern, an amazing young game developer at only fifteen.
Closing remarks and vision for future
What can I say, Game Closure’s future is looking bright. There is such a buzz about the company; heck, I don’t think Michael even sleeps. He’s always in the office or at meetings. Even as they add more and more people to their development team, the passion doesn’t seem to fade (they are even scaling out into a new office to house their growing operation). All I can say is Zynga better watch out, Game Closure has the drive and the talented people behind it to make it a billion dollar company. Going forward, the Flax Project and Game Closure will be solidifying our close relationship; both Carl and I have been invited to return to Game Closure next year as part of our work program, and when the time is right for us, maybe joining the ranks of Game Closure development team permanently.