In today’s post I would like to share with you my experience working on my first cross-platform game. Although it is intended to be available for Windows Phone, iOS and Android, currently I’m focused on the Windows Phone version.
The game is called Muster my Monsters (MmM). It is a two-player fighting monsters action game. It is a casual game, so game mechanics need to be simple and art appealing to most of people. Here you have a gameplay video.
Prototyping is a critical developing phase. During prototyping you may find design problems on your app that, if not detected early, would probably make you and your team waste an important amount of time.
There are a lot of techniques and tools to create prototypes. You can prototype on paper while brainstorming and use sophisticated tools later to create visually appealing prototypes.
However, I decided to use Keynote for prototyping my last client app Aduho Mirror. In today’s post I would like to share my reasons and experience.
Today’s post is an update for an old article about posting high scores to Facebook Wall. Some users have reported some issues about this class. There were some problems with the state control when authorization was needed.
Today I will like to post a new version of the class that solves these issues. The project is now called FacebookScorer and you can find it on GitHub.
About one year ago I wrote an article entitled “Time distribution on game development“. On this article you can read about what tasks I was working on when developing New Sokoban and how they were distributed on time. That post was written a few days before the approval of the game.
A year has gone since then and a lot of things have happened and changed. In today’s post I would like to present a new chart revealing important differences on time distribution on my everyday work. After that, I will try to get some useful conclusions.
Today I would like to share with you a little piece of code that I find very handy. A class that helps you managing “updates”. I use it in my apps that work with cached data. You could encounter the situation where you need to develop an app that queries a web service to obtain the data to be shown on the device.
However, sometimes the information you need to access doesn’t change so often and it is not necessary to bother the user with a loading message only to end up showing the same information than 2 minutes before. If being up to date accurately is not critical for your app, the code I’m going to show may help you.
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’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.
Today’s post is going to be a tutorial-style one. One of the (few) annoying things of cocos2d is the fact that it is very unrelated to UIKit and the Model View Controller paradigm of Apple’s views a view controllers. This is a problem when you need to show, for example, a view controller modally to send an e-mail or show Game Center leaderboards and achievements.
In this tutorial I am going to describe the technique I use to connect with “Apple’s layer” from cocos2d in an easy, modular, reusable way. You will find the project source code used on this tutorial at the end of this post.
