In my experience it's really tough to make an Android app look good. I started building an Android app, but got frustrated trying to muck with XML, never getting anything to layout how I wanted it to. I decided to give Cocoa Touch a try and found that the built in libraries take care of just about everything you need. I probably just didn't give it enough time though. I do plan on revisiting though.
Objective C is a _giant_ pain in the ass, though. Just adding a property to a class means adding four lines between 2 files. I can't even imagine how people coped before 3.0.
I agree about Object-C being a pain, disagree about making Android apps look good.
Perhaps it's a trade off. The iPhone has Interface Builder, we get the shitty eclipse builder (plus the ability to use straight xml, or do it all programmatically).
We get to use Java, but we have to use eclipse. the iphone has to use objective c, but they get xcode.
I disagree about Objective-C being a pain. When I was doing osx development. Desktop and iPhone, I liked it.
You do not have to use Eclipse at all! I use maven and the community edition of IntelliJ IDEA. But I could also use Netbeans. Or a simple text editor. For the GUI you can use DroidDraw.
And you do not have to use Java. You can use Scala. Although I would recommend using Java until you are familiar with the APIs and concepts.
Objective C is a _giant_ pain in the ass, though. Just adding a property to a class means adding four lines between 2 files. I can't even imagine how people coped before 3.0.