Skip to main content

#1GAM - One Game a Month - Jan 2014 - HTML5

No New Year resolutions... but new opportunities to learn.
I've signed up for the #1GAM challenge, as a way of helping get up to speed in the technologies I'm going to need in my new job, chiefly PHP, Java and HTML5.
Last year #1GAM was the spur to encourage the creation of a community of nearly 7000 developers, all of whom tried to develop and post a game a month, resulting in over 5000 games .

The theme for January is: RESPAWN, any platform, using any language, and the idea is to try and attempt iterative development, AND shipping code.
Shipping code has always been my downfall, I dally, I riddle and never get round to actually posting the finished product. Hopefully this will change.
So for my first attempt I'm going to go the easy route, and try an HTML5 app, and a simple game. I've downloaded the Intel XDK, which builds HTML 5 and then weirdly deploys as native apps, on a range of platforms.

I might try and port the Ninja Dinosaur vs Pirate Robot Game... or maybe something simpler

Happy 2014.

Popular posts from this blog


Spine again - animating game assets

Laura Tallarday gave a neat demo of how to build an animation in Spine on the CoronaGeek Hangout, so I had a bash at chopping up an image and animating it.
The plan is to add some more sophisticated animations to the new game "Duck sized horse".. but as was discussed in the show adding a whole bunch of spine animated objects might hammer a mobile device... and as the aim is to have 100 tiny duck sized horses, I'd best choose another approach for them.

anyway here's a swaying viking...

Using Corona SDK

Corona Architecture Overview
Diagram showing the Corona SDK architecture -source Walter Lua - CEO Corona The development process. I built the game "Ninja Dinosaurs vs Pirate Robots" in a series of 4 development sprints. I used a familiar game format, the "Infinite Runner" to guide the overall structure, and built the game using the Agile development methodology and Simplicity principle: "simplicity: write the simplest code to do the job, do not provide hooks in your code for ‘future needs" - this prevents scope creep. Studies by Jones (2009) have shown that Agile is most effective with small teams. Agile focuses on swift iterative cycles creating instances of working code, which are constantly reviewed and guided by the end users rather than a rigid commitment to a fixed system architecture. It values working code over heavy documentation, as might be encountered in a more traditional waterfall development approach.
Game Summary. Whilst the game is an inf…