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.
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.
The lasts weeks I have been trying and playing with different frameworks, methodologies and alternatives to mobile cross-platform development. In today’s post I would like to share with you my conclusions and… headaches.
So, you know, by definition cross-platform development is never an easy issue. Every platform is very different from each other just because it needs to differentiate from the competitors. So you, as a cross-platform developer, have to deal with it. Period.
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.
Pigeons Attack was born as a sample to show how the accelerometer API works. You move forward and backward –tilting your phone- your just washed car in order to avoid pigeons get it dirty. Once the semaphore becomes green, leave quickly the scene to check how many impacts you had. The less you have the better.
Within the following sections you will be guided through the development process, starting from a new Cell SDK project.
Today’s post is going to be the fourth in the series “Game Theory Applied”. You have the previous ones here:
Today I would like to talk about the tricky concepts around puzzles and puzzle-based games like New Sokoban. Puzzles are often considered to not be games at all. This means that designing a video-game entirely based on puzzles implies some issues that need to be addressed to minimize the inherent problems that puzzles have and maximize their benefits. We will see it applied to New Sokoban, a puzzle-solving game.
In today’s post I would like to share with you some thoughts about surviving as an indie iOS developer. I started my iOS journey in August 2009 with the development of paintingWalls. However, I went full-time indie one year later, on August 2010. So currently, I’m living from the incomings produced by the apps you can see in the Projects page of this blog.
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.
