The sheer size and depth of the community that has sprouted up around Unity makes it an absolute no-brainer for someone looking to dive off into development, and I have been pleasantly surprised that the toolset itself holds up to detailed inspection in almost every way. But this post isn't about Android development – I'll save that for later.įor myself, I spent most of December doing some serious analysis of the project and decided that instead of embarking on yet another engine development cycle (I've spent the past 10 years building and licensing custom engines in various shapes and sizes), that I would instead spend a month or two prototyping and experimenting with Unity, which in my mind is the hands-down winner of the engine / middleware battle (at least for the time being). As a team, we've been doing a bit of experimentation with mobile titles (Android in particular), as the barrier to entry is about as low as it gets and we all have hardware. Unfortunately the sales and feedback have been less than what we were hoping for, and the rest of the team has downsized themselves to part-time or less as the demands of paying rent and eating regularly started to creep into play.

In November, we shipped our first game, built using a custom engine and all of the pains and joys that brings.

To begin, I definitely want to mention that I'm far from a 'Unity expert' at this point – I'm still learning and doing a lot of trial and error at this point, but am at the point where I'm at least comfortable enough that I feel like throwing this out there for the community.

3ds max to unity