Stackoverflow with the [android] tag is going to be your biggest resource for q & a in my opinion. Googling for Android dev stuff is a pain as you get a lot of

Stackoverflow with the [android] tag is going to be your biggest resource for q & a in my opinion. Googling for Android dev stuff is a pain as you get a lot of strange and barely useful Google groups threads and clones. As for books, I bought a beginners book to get started, but you're probably beyond that if you have Java experience. The Google examples and dev starter page are enough to get rolling actually. Also, regarding targeting devices; in your manifest, you can set a lowest possible SDK and a target SDK and compile against 1.6, and then allow for the device to do the density control and you can almost target all the devices in one APK. You just have to make sure not to use any code that doesn't work in the 1.5/1.6 versions of Android - but if you're in eclipse, it will help out a little with this. My games are getting downloaded by 1.5 users and Droid 2.x users. I think the thing you'll hate the most right out of the gate is the 24-hour return policy in the Android market - especially since you're coming from iPhone. People can buy your app, but you don't know if it's a sale for 24 hours when it finally closes. In that limbo time, they get to use it for free and just by uninstalling they get their money back - or rather - their transaction never happens. It's great for the end user, but hard to cope with as a developer who thinks they have sales, but overnight they just go away every now and then. I've had up to 25% cancellation rates on bad days. Whatever you are creating, I hope it has repeat value, I think that's one of the only ways to get around the cancellation problem.