Took long enough....
Actually there is a story as to why it took so long for the Shatter Crash Android version to come out, but that's something for another blog post. It wasn't a technical reason though.
Since this is all fresh in my mind, I wanted to share a couple tips on stuff to think about when you do a multi-platform game. This is more oriented for iOS and Android stuff, but will work for any other platforms as well
- Port your game to the new platform. This is pretty obvious. I use Unity3D which handles 99% of the stuff for all the different platforms.
- You should look at the new platform and learn if there are a particular nuances of the platform you should try to handle. One example, on Android hitting the back button on the main menu generally pops up a quit dialogue giving the user an ability to cleaning quit the app, not just put it into the background
- Handling product/app store links for the new platform. For Shatter Crash I added a 'Rate' button so users can rate the app. On iOS this takes the user to the iOS ttore list, for Android it takes the user to the Google Play listing. Ideally you can take advantage of a mechanism so the app uses the proper links automatically depending on the platform.
- Handling UI layouts for different platforms. The iOS devices are pretty nice because you only have a handful of UI resolutions and aspect ratios. All iPads are 4:3 aspect ratio, and iPhones/iPods are either 3:2 or 16:9. Android obviously has a lot of different aspect ratios. Ideally your UI can automatically handle scaling and moving widgets to take advantage of the screen for particular device it's running on, rather then you manually placing the widgets for every possible screen size
- Way to direct users to the different store pages - When you go from 1 platform to many, you need to make it as easy as possible for people to find the version of the game relevant to them. One idea here is make a page on you website with links to the different stores you game is on; then make sure to SEO the hell out of said page so it's highly placed on search engines.
- Achievement/Leaderboard/etc. - Competitive features like leaderboards and challenges, plus achievements for the collector-mentality players, are definitely nice to have in your game. Different platforms generally have different implementations of these, which can be annoying to manage. I created an internal API which my games use for handling leaderboards/achievements/challenges updates and unlocks. That API in turn works with a binding layer responsible for interacting with the platform-specific system. In this way I can build in support for all those features, then the platform binding layer handles how the nuances of converting that to the platform game system format