The beauty of IB (along with pixel-perfect layouts since there are only 3 devices) is that our designer can checkout the project and skin the app and not have to touch code. Yes, there are something that IB can't handle (try passing a managed object context to a view controller in a tab using IB) but you can do anything you want in code.
In Android, there is no IB. Closest equivalent is someone's project called http://DroidDraw.org. Since there is no IB, it is all code. XML is more code than meta-data when it comes to defining views. To make an equivalent UI in Android that is pretty as the iOS one requires a lot more unit effort than in iOS (and a lot more of that coming from the developer).
The closest equivalent to IB in Android is actually built into the standard Android dev toolset (the Android Developer Tools for Eclipse).
Droid Draw has been abandoned for years. The visual UI tools in the latest releases of the ADT is actually pretty decent. Probably not as good as what I've heard about IB, but not bad. Certainly better than Droid Draw ever was.
In Android, there is no IB. Closest equivalent is someone's project called http://DroidDraw.org. Since there is no IB, it is all code. XML is more code than meta-data when it comes to defining views. To make an equivalent UI in Android that is pretty as the iOS one requires a lot more unit effort than in iOS (and a lot more of that coming from the developer).