For example, Skype: http://i.imgur.com/4XwVmjy.jpg
Responsive design is one of Android's most fundamental design principles. It just took a while (and a few million tablet sales) for developers to take the platform seriously.
Most new android apps are responsive these days. And those companies that maintain their existing apps are busy adding big screen support.
I'm glad to hear that companies are busy adding big screen support, though that support is arguably coming late. The main point is that an Android app's interface could be stretched across anything, and this has certainly been a design obstacle in the past.
I just posted two screenshots showing otherwise.
> Android's fragment API makes it a lot easier than he iPad to adapt to a proper tablet UI if you want.
And this is just ridiculous. Regardless of whether you prefer iPads or Androids, iPads are most decidedly easier to design tablet UIs for because there are so few screen sizes.
It's true that AutoLayout's systems of interdependent linear equations are strictly more powerful than Android's structural layouts but they're a far more awkward solution to the vast majority of common UI layout problems. In practice Android UIs are far, far easier to write and maintain. Debugging the kind of complex AutoLayout schemes you describe can quickly become a nightmare. The structural approach taken by Android and WP is far more natural for the kinds of UIs you actually find in the field.
Also, Android's CSS-like style system makes it far easier to define app-wide constants like grid spacing, margins, button padding etc and to change them in one place.