Hello, this post aims to summarise my experience with the challenge I set myself: creating an original game for Android in the shortest possible time.
The initial goal was to finish it in a week, but in the end I had to spend nearly three weeks on it, mainly because of changes I wanted to make to the difficulty, the implementation of services I had never been responsible for implementing before, and other responsibilities that forced me to spend less time on development on certain days.
The game belongs to the casual genre simply because the only goal is to survive for as long as possible by killing zombies while preventing them from reaching the survivors' cabin in a mini-world lowpoly.
The first task was the 3D design; I set about modelling all the elements I wanted to use in the game, texturing them and, in the case of the zombies, rigging them y and animating them. I chose a low-poly aesthetic not only because I love its visual appeal but also because I think it is a more affordable style when time is a factor to consider. The zombies are inspired by the voxel style of the Minecraft zombies but with less pronounced edges.
During modelling I paid close attention to keeping the topology of the models optimised for the game, no tris or ngons and I kept an eye on the poly-count of each model, since I wanted a smooth-running game for Android phones.
Once the 3D design was done, I went back to Unity, where I set to work on the game logic. At first, my inexperience made me wonder whether it was worth moving the planet instead of the camera, but I quickly ruled that out when I saw that it would affect the rigidbodies I wanted to use for the zombies. I had to figure out how to write a script that would let me move the camera around the whole world simply by sliding my finger across the screen. The result was this:

To program the zombies' movement around the scene, I created some spawn points and breadcrumbs for them to follow. There is a limited number of paths they can choose, and once they pick one they follow it to the end (the cabin). When I tested the game after implementing this, along with the zombies dying when squashed, I realised I did not want to give the player so much freedom to move the camera around the whole planet. The reason was that it would be very easy to position yourself where all the paths were visible and finish off all the zombies effortlessly. I was a little sorry to have to limit that feature because I liked the idea of being able to place the camera anywhere, but once I tried the game with that restriction I realised it was a good move, and the game challenged the player again by forcing them to keep moving.
Later on, thanks to the advice of the people who tested the game before it was published, I decided to make a few changes, such as giving the enemies a larger hitbox and making sure the text on the buttons did not confuse the player.
The final result is as follows:
For the ads I decided to use Unity Ads and for the leaderboard Google Services, implementing these services was an enriching experience from which I learned a lot. I decided that the ads should reward the player when they pressed the «extra life» button, since they have been shown to be better accepted by users.
In the end the game came out once I had implemented Unity Analytics and decided it was time to put an end to all the time I had devoted to shaping the project. In the future I may add more features that were left on the drawing board, but that will be another story.
This experience has served to test myself and, above all, to improve in more than one field. My conclusion is that game development involves many roles, and it is difficult to focus on all of them. I keep stressing that my main role is tied to design and not to programming, and that is something I will try to work on and make more of. In any case, it is always good to know other roles: it helps to make your teammates' work easier and easier to understand, and it lets you go further with greater confidence.


