In the summer of 2014, I decided to build a game. I love history and knowledge so I decided that the game was to be trivia. I started building a site using PHP and MySQL (which I learned just for this purpose) to store facts, questions, and other info.<\/p>\n
By the end of summer, I had started building the website. Having to split working on this between school and my work at a restaurant, it took a while for me to get the site done before I could move on to the actual trivia app.<\/p>\n
The spoiler to this story is that the final game I ended up building and releasing to the App Store was a totally different app<\/strong> that had nothing to do with trivia. The whole experience was full of ups and downs that I figure I should write about what I have learned along the way.<\/p>\n While I was building my trivia database and website for the trivia game, I found a lot of cool facts that I shared with my friends in class. In one such sharing, a friend showed me this game called Trivia Crack<\/em>. My jaw dropped \u2013 it was almost the exact same game that I was trying to (but not yet) build at the time.<\/p>\n What\u2019s worse is that my game wasn\u2019t going to be nearly as great<\/strong> as Trivia Crack. <\/em>I also didn\u2019t want to seem like I was copying them so I had to change gears and come up with a better idea for a game.<\/strong> This is only the first of the many changes I have to make (most of the time, reluctantly) in building my first own game.<\/p>\n That said, letting go is harder than it sounds<\/strong> and is never an easy thing to do. By then, I had spent a lot of<\/em> time learning PHP and MySQL<\/strong>, and not to mention all that time building the website for my trivia game. Stumbling upon Trivia Crack<\/em> left me in a rut \u2013 I spent the rest of that class thinking about what I was going to do.<\/p>\n I was really bummed about Trivia Crack<\/em> beating me to the market. I thought I was really on to something, but I was too late for the game. At that moment, I realized that I could do one of two things.<\/strong><\/p>\n I could sit there and pout about Trivia Crack,<\/em> or I could take action and start a new project right away<\/strong>. The former is counterproductive at best, and I realized that if I ever wanted to get a game on the App Store, I just had to move on.<\/p>\n There is a lot more that goes into making a great game than most people think. You have to take the time to go through the games that made it to the App Store and more importantly go through the top downloaded games list to find what they have in common<\/strong>. You want to look for things like how players control the game, how difficult the game is, and of course, you also want to make sure nobody has already made your game.<\/p>\n Find out what people enjoy, but don\u2019t be afraid to make your own path<\/strong>. The lesson here is to always do your research<\/strong> and never stop learning<\/strong>. There is still so much out there you don\u2019t know.<\/p>\n In finding a new game idea to release, I did a lot of research on game development and studied games like the 28-day success story, Flappy Bird.<\/em><\/p>\n From the process, I came up with a rough sketch of a soldier skydiving, while dodging bullets that were shot up at him. Soon after, it became the soldier dodging bullets falling from<\/em> the sky. I liked the direction I was going in, but something was missing. I wanted the game to feel<\/em> impossible but actually wasn\u2019t, something I learned from my research<\/strong>.<\/p>\n So I sat down with my dad aka advisor and we discussed the game. That\u2019s when we came up with the idea to let the soldier dodge bullets but catch nukes. It was perfect. But there was still so much to do.<\/p>\n As development continued, I realized that the game art was too complicated<\/strong>; something has to change. Eventually, I stripped the idea of having a soldier be the protagonist, down to it just being a blue ball. The blue ball sprite was leftover from an old project I was doing back when I was teaching myself to code.<\/p>\n Then, it all became clear to me. Shapes! I will make Shapes the theme of my game: the soldier became a small blue ball, catching bullets that turned into circles and dodging nukes that turned into triangles and squares.<\/p>\n Shapes are simple, appealing, easy on the eyes, and makes it easy to relate to no matter what age my players are<\/strong>. And like the game art, I also kept the game controls easy and natural<\/strong>; just a tap on the screen can go a long way. Simplicity works.<\/p>\n After all that, I built and released my first game: 3-Shapes\u2026 and made a few more mistakes along the way.<\/p>\n During the first week in the App Store, I felt like my app did very well; it was downloaded over a hundred times. This was without any real PR or marketing<\/strong>, just solely word of mouth. However, I notice a trend. People played the game a couple of times before they just gave up for good. I would then have plenty of people tell me the game was too hard.<\/strong><\/p>\n At this point, I had two regrets: the first was not doing a soft release. A soft release can be helpful in so many ways. Releasing the game to only a handful of your friends allows you to find bugs and fix them quickly<\/strong>. The first day I released 3-Shapes, two very \u201cbig\u201d bugs were found right away. If I had done a soft release I would have been able to fix those bugs and have a smoother official launch.<\/strong><\/p>\n I mentioned that players have been abandoning my game because it was too hard, almost impossible actually. The average player didn\u2019t do well, and would understandably give up. The thing is I knew this was going to happen<\/strong>. My sister had been telling me that the game was too hard before<\/em> I had released it. I should have made it easier before<\/em> the launch but I was reluctant.<\/p>\n From my<\/em> perspective the game was too easy. I spent so much time playing it myself to test for bugs so I have pretty much mastered the game. But I am building the game for<\/em> my players. You have to remember to look at the game from the player\u2019s perspective.<\/strong> If they give up on your game, your game won\u2019t go far. Develop from the player\u2019s perspective, you can\u2019t always be right.<\/strong><\/p>\n When developing a game having a time frame helps to keep yourself on track. If the game isn\u2019t ready to be released, don\u2019t release it<\/strong>. If there are things you want to add, that you could easily add in an update, get that done, and put it in the game.<\/p>\n I learned this the hard way: I wanted to add a feature to the game that allows you to win new heroes when you reach a current high score. I felt that the game would have been a lot more fun to play if the players had that goal of reaching the next hero. Yet I didn\u2019t<\/em> add that to the game as it would mean a delay of a week or two for the launch<\/strong>.<\/p>\n In retrospect, that would have helped me retain more players as it will become a personal challenge for them. But basically, make sure you love what you are releasing<\/strong>. Otherwise, don\u2019t release the game<\/strong>, even if it means you will miss your deadline by a small margin.<\/p>\n If you are waiting for me to tell you how much of a success my game has become, later on, I\u2019m just going to spoil the ending for you and say that 3-Shapes didn\u2019t make me millions (surprise!). I did not expect to make millions<\/strong> off this game (it\u2019s only my first) but I wanted to learn and do something I enjoyed \u2013 and I hit the ball out of the park with this one.<\/p>\n When developing a game or app or anything in that matter, do it for fun<\/strong>. Not only will you get a better product, but you will also be more proud of that product, app, or whatever it eventually becomes. And it will be built for the right reasons, with the right focus.<\/p>\n The journey is the reward.<\/p><\/blockquote>\n When I was building my app I expected to learn some code but in my journey, I learned a few other things that are just as valuable and no less important<\/strong>. At the very least, these lessons will probably make my next app-making process, and probably yours, a whole lot easier.<\/p>","protected":false},"excerpt":{"rendered":" In the summer of 2014, I decided to build a game. I love history and knowledge so I decided that the game was to be trivia. I started building a site using PHP and MySQL (which I learned just for this purpose) to store facts, questions, and other info. By the end of summer, I…<\/p>\n","protected":false},"author":541,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3399],"tags":[3214],"topic":[4521],"class_list":["entry-content","is-maxi"],"acf":[],"yoast_head":"\n1. Your Plans Will Keep Changing<\/h2>\n
2. Be Ready To Let Go and Move On<\/h2>\n
3. Do Your Research<\/h2>\n
4. Your Game is Going to Evolve. Let it.<\/h2>\n
5. Keep it Simple<\/h2>\n
6. Do a Soft Release<\/h2>\n
7. Listen to Your Players<\/h2>\n
8. Don\u2019t Rush Your Project<\/h2>\n
9. Don\u2019t Expect to Make Millions<\/h2>\n
Conclusion<\/h2>\n