GAME JOBS
Contents
Revisiting Android
 
 
Printer-Friendly VersionPrinter-Friendly Version
 
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
June 6, 2013
 
Wargaming.net
Build Engineer
 
Gameloft - New York
Programmer
 
Wargaming.net
Build Engineer
 
Virdyne Technologies
Unity Programmer
 
Wargaming.net
Quality Assurance Analyst
 
Wargaming.net
Python Developer
spacer
Latest Blogs
spacer View All     Post     RSS spacer
 
June 6, 2013
 
Free to Play: A Call for Games Lacking Challenge
 
Cracking the Touchscreen Code [1]
 
10 Business Law and Tax Law Steps to Improve the Chance of Crowdfunding Success
 
Deep Plaid Games, one year later
 
The Competition of Sportsmanship in Online Games
spacer
About
spacer Editor-In-Chief:
Kris Graft
Blog Director:
Christian Nutt
Senior Contributing Editor:
Brandon Sheffield
News Editors:
Mike Rose, Kris Ligman
Editors-At-Large:
Leigh Alexander, Chris Morris
Advertising:
Jennifer Sulik
Recruitment:
Gina Gross
Education:
Gillian Crowley
 
Contact Gamasutra
 
Report a Problem
 
Submit News
 
Comment Guidelines
 
Blogging Guidelines
Sponsor
Features
  Revisiting Android
by Patrick Miller [Programming, Game Developer Magazine, Console/PC, Indie, Smartphone/Tablet, GD Mag, GD Mag Exclusive]
1 comments Share on Twitter Share on Facebook RSS
 
 
May 28, 2013 Article Start Previous Page 7 of 10 Next
 

Hidden Variable Studios

Charley Price (CCO)

Prior dev background (platforms): GBA, PC, Xbox 360, PS3, Flash, iOS, Android
Shipped Android titles:
Bag It!
Preferred toolset:
Unity



Is fragmentation still a major issue for you? Which devices do you target?

It's always a worry, but in some ways the variety of devices is so broad, it pretty much demands that you define your min spec criteria early in the development process so you can make sense of it all. Given that we simultaneously develop for iOS as well, our min spec decision hardware-wise on that platform helped to implicitly inform the min spec choices we made for Android.

Knowing the risks of different screen sizes/aspect ratios, we've developed our titles with floating UI elements that anchor (or are positioned relative to) the edges of the play space, and made sure that slight variations in viewable space don't impact gameplay dramatically. As such, when new devices and aspect ratios were released, we've generally been able to support them right out of the gate.

As for devices, a combination of App Store data and Flurry analytics gives us a pretty good sense of what types of devices are being used to play our game. As such, we tend to focus much of our attention on our first-gen NOOK Color and Kindle Fire (among our most popular devices with narrow aspect ratios) and our Nexus One (as a min spec).

Do you have any tips for optimizing the Android dev process?

Most of our Android-specific notes end up being directly related to our experiences developing in Unity. For example, many of the risks of creating Android-specific plug-ins can be mitigated using inexpensive, off-the-shelf solutions from sites like Prime31.com.

Going into more detail, one of our engineers, Clark Kromenaker, wrote up some thoughts on his blog about some of the pitfalls inherent in storing data on Android devices (for example, local memory vs. SD card memory), which would likely be a good read for new Android devs.

How have your games sold on Android?

We first released Bag It! back in late 2011 on both iOS and Android simultaneously. Since then, we have released it on almost a dozen different Android app stores, both worldwide and foreign territory-specific (including Samsung, Mobiroo, and Fuhu to name a few less-common examples), but the only ones that have really generated a meaningful financial return for us thus far have been Google, Amazon, and B&N NOOK.

Overall, our iOS versions of Bag It! have outperformed our Android SKUs in terms of total downloads 7:1 (although if you remove one big iOS promo event it's closer to 3:1). However, if you just count paid downloads, iOS and Android as a whole are neck and neck (with iOS slightly ahead). That said, IAPs still favor iOS, with almost a 3:1 advantage over Android.

These numbers are generally pretty surprising to fellow mobile devs, many of whom have opted to eschew Android as a platform for fear of lack of sales. In particular, both Google Play and B&N NOOK have been pretty equal in terms of sales, both outperforming Amazon by a reasonable margin. One of the reasons we suspect we've been so successful on the B&N NOOK store is the fact that it currently only supports premium games (with free "trial" versions available for full titles). As such, as a premium title, you're able to avoid the glut of freemium games on other platforms, which allows you to stand out a bit more.

 
Article Start Previous Page 7 of 10 Next
 
Top Stories

image
Keeping the simulation dream alive
image
A 15-year-old critique of the game industry that's still relevant today
image
Here's the first list of Unreal Engine 4 integrated middleware
image
Amazon launches dedicated indie games storefront
Comments

Maurício Gomes
profile image
I will ADD a comment here to contribute for the article.

I am co-owner of Kidoteca, we released 3 paid apps and 4 free apps so far. None of them use IAP or ads (some free apps just point to our paid apps, in a hidden section, because we target kids and think making ads for kids is horrible and evil)

We have much greater "conversion" on iOS...

But overall we are doing better on Android, although people there are much more tightfisted, and for example do not buy stuff on launch, and conversions are low, over time Android always surpass iOS, specially because the fairer ranking system, and much better search engine, iOS ranking system is too volatile and hard to stay on it if you don't have a marketing budget (and for now, we don't).

Also regarding fragmentation, sometimes we have some silly issues, but is usually on one specific device or another... although ironically the problematic device is usually the same one (any version of Galaxy Tab, they always misbehave in some way or another, it seems Samsung have terrible driver coders...)


none
 
Comment:
 




UBM Tech