Today’s article is the second one in the series “Game Theory Applied”. You can find the first article of the series here. Today I would like to talk about game rewards, and how I applied them on New Sokoban.
Game rewards are a very important concept in game design. Actually, in some sense, players play games to be rewarded. It is a human need. Players need to be evaluated favorably. That’s why a well designed and balanced game rewards system is key in any game, even for the simplest one.
Some months ago I wrote an article on this blog titled “Tools for creating a game“. On that article I talked about the tools I used to develop my first iOS game New Sokoban. The message of that article was summarized with this mental note:
Mental note: always use existing tools. If there is a tool that barely fits your needs use it. You will be amazed about how quickly you adapt yourself to that tool and how your productivity increases.
However, currently I’m working on a new game that needed a very specific and game dependent developing tool. So, unfortunately, I spent about two weeks developing, testing and refining a development tool for my new game. In today’s article I’m going to share the experience.
In today’s post I’m going to share a piece of code that allows your games to easily connect to Facebook. It is a singleton class designed to be reusable, very simple to use and with only one task in mind: post new high scores on Facebook. You can find the example project source code at the end of the article.
The aim of this post is not to teach you about how to use the Facebook API to connect your iPhone games to Facebook. There are a lot of articles covering this topic and the official Facebook developers site. In this tutorial I would like to put the emphasis on the reusable and simplicity to use aspects. It is very easy to integrate in your projects the piece of code I’m going to show you.
In today’s post I would like to start a series of articles about Theory of Game Design and how I applied (or tried to apply…) it to my projects. Usually games are made by inspiration and intuition. And this is not a bad approach because, at the end of the day, game creation is a deeply creative activity.
However, there are some game design aspects that have been theorized by experienced game designers that, despite sounding quite obvious, it is worth to keep them in mind while working on our games. I would like to start by one of the most interesting and effective concepts of game design: The Flow Channel. Applying this concept to New Sokoban had a very positive impact on the games experience. Despite it being an intuitive aspect of games that you could have learned while playing a lot of games during your live, the first time I red about it was in Jesse Schell’s book The Art of Game Design. By the way, this book is highly recommended for game designers out there and wanna be game designers like me 😉
In today’s post I’m going to explain a little bit how my routine as an indie dev has changed in the last few weeks. I have experienced a really big change since New Sokoban was presented and released. I have gone from the lone wolf indie dev style to an intensive collaborative working style. And only in 2 months!
This is my first article that is going to be included into the iDevBlogADay series. So, I would like to encourage you to read the About page and the Welcome post if you want to know a little bit about me. You can also find all my own iOS projects on the Projects page.
I started my own App Store journey as an indie about 18 months ago. It has been an incredible experience, with lots of satisfying moments and also some frustrating ones. With successful stories and also with non so successful ones. However, the most important thing is that I have learned a lot about living in the jungle of the App Store. In today’s post I would like to share some experiences with you.
