[Zigurd]

The first thing I tell designers and coders with iOS experience is to get over trying to make your layouts pixel-perfect. It's such a simple thing. But so many projects end up wasting a lot of resources, or even end up locking screen orientation when they first ship because they didn't take this seriously.

The other side of this coin is that a simple wireframe can get implemented on iOS quickly, while on Android, the coders may spend a lot of time on multiple layouts, multiple sets of graphical assets, different font sizes, different screen dimensions and densities, etc. It often helps if the designer participates in creating and testing layouts and assets for an Android version.

Secondly, a lot of coders who don't also have some server-side Java experience find Eclipse jarringly unfriendly. Spend some time getting used to Eclipse and understand how the "It's plugins all the way down" model makes Eclipse do some stupid things. Android Studio is much better, but it's still an "early access" release.

Thirdly, Android's runtime is a platform for apps and system middleware. Large parts of the Android system are written in Java using the same toolchain as apps. You can, for example, add an API to Android that other apps can use. You can communicate with lots of other apps. You can "borrow" parts of apps' UI and ask them to do particular tasks, like picking a file, for you, and you can let other apps do the same with your app. Android is more complex because it is more expressive.