Javoscript

Programming, technology and more...

Lessons learned at my first game jam

1 year ago · 3 MIN READ
#mvp  #game dev  #javascript  #mobile 

A few months ago, me and two fellow indie hackers went to a local game jam, in which the only requirement was to make a game with the motto: “it wasn’t designed for this”.

We already knew we wanted to make a mobile game (iOS/Android), so we rapidly thought the game mechanics, sketched our game and went on to code it. Since we already had experience with these technologies (and they suited our needs), we decided we were using HTML5 + JavaScript for making the game and then port it to the different platforms (iOS and Android) using Cordova. As a game engine, we used Phaser.io, a pretty simple JavaScript game development framework / engine, which served us really well.

We ended up with a game in which you use a clock to waste time (it clearly isn’t designed for that), and by the end of the game jam, we already had published it to the Android Play Store (and a few days later to the Apple App Store).

Here are some things I learned from this first-time experience in making a game and attending a game jam:

  • Enjoy the whole ride: if you are spending a whole weekend (in our case) into making a minimum viable product (or, if you can, a finished deliverable), it has to be something you like building. From the very beginning of our game design stage I was already liking the idea of the final product. Even if we weren’t able to finish it in that weekend, I knew I was going to have fun the two days I was spending into thinking, designing and implementing our game.
  • Use technologies you feel comfortable with: given the short time you have to think, design and code, it’s not a good idea to learn a whole new stack of technologies in these kind of events. Stick to what you know.
  • Use the tools at your disposal: as developers, we all love building our stuff from scratch, having full control over out entire codebase. But sometimes it’s a good idea to trust already established tools to move faster and have a deliverable product with less effort.
  • Don’t overthink every choice you make: maybe the way you decided to structure your code isn’t fully scalable. Maybe you could have implemented the sprite system in a more optimized web. Maybe your game isn’t taking full advantage of the tech’s potential. There will be time later to focus on all these things. Right now, you have to consciously oversee these issues, and move forward. You have to move fast.

You need an MVP: before the game jam ends you need to, at least, have the first iteration of your game working, with full mechanics and playability. It’s important to leave the event with a solid foundation of your game. Having a finished playable and fun prototype will give you future motivation to keep working on it, to optimize all those rough edges you left unpolished, to show your game to other people and ask them what they think of it. If you leave without a working prototype, you’ll probably never engage again with the idea of investing your time into it.

We are always looking for some more inputs and traction, after all our relatives and friends have tried it, with pretty much good feedback. Obviously, the game is still not complete, and we have many ideas of things we want to add to it, and bug fixes we have to make, like improving the graphics and sound effects, adding more power ups, etc.

I’d really appreciate if anyone is willing to try it and give some more feedback. The game is in Spanish (we are from Argentina), but it's definitely not language dependent.

The links to the app stores are:

···

Javier Ugarte

Entrepreneur & developer
comments powered by Disqus


Proudly powered by Canvas · Sign In