Native debugging is the worst culprit. Yes, that's precisely what I mean. The argument was that it's more developer-friendly, and this is one of the areas in which it isn't. So we're agreed then. Funny to think that when I made my previous post, there was still such a thing as Google Wave. Well, these are costs which are dwarfed by your development time. If it takes an extra day of work to complete your android port, you've already blown through the cost of a second-hand mac mini from ebay. And you haven't factored in the cost of a single ipod touch, vs a clutch of off-contract android devices. I'm just going by personal experience. iPhone: several SKUs over 18 months and countless updates. The only time I didn't have a version sail through was when they found a bug in the way the app handled changing orientation, and they gave me steps to reproduce and a link to the relevant documentation covering the issue. Android: They'll accept the $25 fee wherever it's paid from, but try to publish and I'm blocked because I'm physically located in the wrong first-world western democracy. Yes, that's true. If it weren't for the geo-blocking, I'd be all over Android. The other drawbacks certainly aren't enough to stop me, and my whole business strategy is 'be on everything'. But I chimed in on this thread because it was claimed that android is better, cheaper, easier for developers - and it really doesn't look that way from where I'm sitting.