BitFlip Games

Editor’s note: This is part 5 in a 5 part series outlining our experiences with Unity & Unity iPhone. Be sure to check out Part 1, Part 2, Part 3, and Part 4. Our first game, Ace Attack, is an iPhone game based on the card game War.  This posed a big challenge for us, [...]

Editor’s note: This is part 4 in a 5 part series outlining our experiences with Unity & Unity iPhone. Be sure to check out Part 1, Part 2, and Part 3. Unity is like a big, old playground.  It’s easy to play with all of the toys and have fun, but you can very easily [...]

Editor’s note: This is part 3 in a 5 part series outlining our experiences with Unity & Unity iPhone. Be sure to check out Part 1 and Part 2. So now we have our projects in source control, and we have a “Library Manager” as the gatekeeper to the Library directory.  If your project is [...]

Last time I talked about what parts of a Unity project need to go into source control, and alluded to some issues that can crop up due to the way that Unity works.  Today I’ll delve into some of the details of what’s going on, why it causes problems, and how to avoid those problems [...]

Game projects, no matter the size, tend to follow a predictable pattern in their development.  At first, work is slow, and you’re happy if you can get anything up on the screen (at Flagship Studios, there was a photograph that somebody took of the first triangle displayed with the engine).  At that stage, a lot [...]

Today I’m going to take a little time to talk about the philosophy of game-building tools and how we approach such things at BitFlip Games. The tools used to make a game can drastically affect the outcome. In our years in the game industry, we have seen some fantastic toolsets. We have also seen tools [...]