Skip to main content

App stores are good for games

By now I think most gamers have bought something from an App-store. Steam, Xbox live Marketplace, iTunes or whatever.

Furthermore I think a lot of people have bought games from places like Apple's app-store but do not consider themselves gamers. So app stores are all the rage now and with Steam now available on the mac it becomes the de-facto PC place to buy games. proprietary platforms all will come with their own. It's seen a boom in independent and low budget games going through a huge surge in market that hasn't been seen since the shareware days.

But even more so for games than other software. Look at the statistics from apple's apps and you find games are number 2 in size. Second only to books which may get kicked out now apple has their own iReader system. So all these app stores regardless of platform or format are a boon for games.

But why games? Honestly I'd love to know myself. There's something about open source that has made it difficult for games to get traction but hasn't been a problem for lots of other software. So this paid model allows lots of wanna-be-game-developers to give it a try with minimal investment and risks. Combine that with the affordable luxury of buying a game for a few dollars instead of over a hundred and you have a thriving marketplace. And good on them! I look forward to seeing where this goes.

Popular posts from this blog

When Agile is not common sense

It's been about 8 years since I got my Agile training from James Grenning and started an Agile Pilot with my team. Right from the start I was super keen and got people practising TDD and Pair Programming even though I didn't really know if that effort would pay off. I just knew we had lots of problems with the old way so I wanted to embrace the new.

So I'd run my own little sessions with the broader team in Sydney sharing Agile concepts and ideas. Giving us a chance to discuss things and keep learning long after James had left. But often I would present new ideas and a few people in the group would respond "oh of course, that's just common sense". Initially I thought it was great as they were embracing these ideas as valuable even though it was not what we were doing before. But after a while I started to get frustrated because they we're not really listening. If some small part of a concept fit nicely with their "common sense" then they took th…

Setting up Fitnesse on Ubuntu in 7 steps

Some pretty basic steps but just to make sure it's here for everyone to see. Setting up fitnesse and running the jar is easy enough. Just go to and get started and do it on your desktop just to see it in action. But for me that wasn't good enough I wanted it to run as service on ubuntu.

I stole a few tricks from how ubuntu runs jenkins and setup fitnesse a similar way.

1. Create a user and group for fitnesse (optional)
I didn't do this because I wanted tomcat, jenkins and fitnesse all running as the same user. Call it laziness to avoid any permissions classing but it doesn't change the process that you need to create or choose what user you're going to make it run as. Don't make it run as your user or root!

2. Download the jar file and place it in /usr/share/fitnesse
Make the folder too of course. It can belong to root as long as the fitnesse user has read access

3. Create the folder to run in at /var/lib/fitnesse
Fitnesse user needs write…


So most of the tests I'm writing now in Fitnesse are using RestFixture. Being able to do all this black box style testing has helped me get a lot of tests up and running without having to change the existing code base. Now I've taken a step future with my own little fork so I can use scenarios and build nice BDD style scripts. But first I want to give me own quick guide to using RestFixture

Step 1: Installing
You can dive straight in by grabbing the latest jar files for RestFixture here
If you know what you're doing can get the nodep version to work nicely along side other libraries you may be including in Fitnesse. But I grabbed the 'full' version and unzipped it into a RestFixture folder alongside my FitNesseRoot folder.
Step 2: Write your first test
I took advantage of the built in Fitnesse api as a basic test and wrote a page called RestFixture with the following contents
!define TEST_SYSTEM {slim} !path RestFix…