Unity

I’m using Unity to develop Project Smart Birds. Why Unity?

The game will be initially for iOS, but after that initial release I want to port to Android, PC, and Mac — and later on, perhaps other platforms too. To increase my chances of success, it’s important that I reach as many potential players as possible with as little extra work as possible. So using some sort of multi-platform SDK was a given. I researched my options, and Unity won out for these reasons:

  • It uses C#, which I have experience with from using XNA.
  • It supports a LOT of platforms, including web browsers and consoles. They support more platforms than any other SDK I could find.
  • Since it is already on the PS3 and 360, chances are good that it will be supported on the PS4 and 720 as well. Not that I’m anticipating going to these platforms anytime soon, but good to know that they’ll likely be an option.
  • Unity the company is established and successful. They’ve been around since 2008 and continue to grow. Sure, any company could tank unexpectedly, but all signs I can see point to this company to continue to exist and support the technology that I’m tying myself to.
  • A lot of companies are looking for Unity programmers. If my indie stuff fails, experience in Unity could help me land a job elsewhere.

The main con for me is that — right now at least — I’m making a simple 2D game, and Unity is more complex than it needs to be for 2D-only games. But luckily, Unity’s asset store has some solid 2D systems that are pretty inexpensive (I’m going with 2D Toolkit), and these help make this issue mostly moot.

All told, I believe that of the available options, I have the best chance of success — both immediate and longer term — with Unity.