{"id":1461,"date":"2012-12-04T21:31:51","date_gmt":"2012-12-04T20:31:51","guid":{"rendered":"http:\/\/www.frozax.com\/blog\/?p=1461"},"modified":"2015-04-04T19:43:52","modified_gmt":"2015-04-04T19:43:52","slug":"developed-released-mobile-game-45-hours","status":"publish","type":"post","link":"https:\/\/www.frozax.com\/blog\/2012\/12\/developed-released-mobile-game-45-hours\/","title":{"rendered":"How I developed and released a mobile game in 45 hours"},"content":{"rendered":"

\"icon_96_transparent\"<\/a>Developing a game always takes longer than expected. I made an experiment and tried to develop a simple but descent game quickly, while keeping tracks of time spent on each feature. I also wanted short development times to see if I can make a profitable game, even if I were paid for it (I’m not doing this for a living, just for fun).
\nThis experiment ended with the game Hashi Puzzles: Bridges & Islands<\/strong>, available right now for Android<\/a> and iPhone\/iPad<\/a> (free download).<\/p>\n

Simple design<\/h3>\n

In order to release the game quickly, I had to have a safe design, without too much risks. I therefore came up with the idea of implementing a game of Hashiwokakero<\/em> (Wikipedia<\/a>), a logic game made by the inventors of sudoku. I know the “gameplay” has already been tried and it’s fun: I won’t need to spend time iterating or tweaking the design.
\nAs I’m not an artist, this is also a good choice because it is graphically simple. I initially planned to do all the art myself, but my brother (Vincent<\/a>) nicely offered his help when I gave him an early build of the game. He therefore made the game icon and logo. He also worked with a tight deadline (1 day).
\nTo have a complete and polished game, I added levels, level packs, hints and a progression (inspired by the great game Flow (Google Play<\/a>, AppStore<\/a>)).
\nI also integrated ads that are removed when the player purchases any of the six purchasable level packs. Purchases are made with in-app payments.
\nThe game has no music, and only very basic sound in the menu (actually, the code used to play the validation sound in the mainmenu is in my framework so it was faster to keep it than to remove it).
\nThe game is translated in French and English. [By the way, if you can speak any other language, feel free to contact me as I’d love to port the game in other languages. The game has very few texts, as you can see on the editable texts sheet<\/a>, and a simple description on the stores<\/em>].
\nWith the design in place, experience gained from a released mobile game (Don’t Feed the Trolls<\/a>), and an engine ready (cocosd-x<\/a>), I can start the actual development of the game.<\/p>\n

45 hours<\/h3>\n

I worked on the project part-time, mostly in the evening when my kids are sleeping ;).
\nThe android version of the game was made and released after 45 hours of work distributed in 11 days. I don’t count the time spent thinking about it in the shower, though \ud83d\ude42
\nI then spent another 5 hours to port, build and submit the iOS version. In addition to creating the project, I added a feature on iOS that I didn’t implement in my previous game: the ability to use iAd<\/a> as well as AdMob<\/a> as advertising sources.
\nIt also took 5 hours for the Amazon App Store Kindle version (it’s in review right now and should be available in a few days). It was the first time I implemented the in-app API for Amazon, that’s why it took a bit longer than it should have.
\nMy brother spent a total of 5 hours on the art (on the last day).<\/p>\n

Total breakdown per feature and sub-feature<\/h3>\n

Here is the time spent per feature:<\/strong>
\n\"feature\"<\/a>
\nI included everything in this chart : my work, the artist’s work and the ports to iOS and Amazon. This is a total of about 60 hours. We can see the distribution is quite even between each feature.
\nIt’s more interesting to see a sub-feature breakdown:<\/strong>
\n\"subfeature\"<\/a>
\nA few comments about this chart:<\/p>\n