Hey HN, (author of that article here) was wondering if you guys had any general feedback. I'm an evolving tech writer and I'm always looking for pointers.
Regarding #8, have you explored the way that "Alternate Resources" [1] allows you to better handle fragmentation issues? I've found it at least to be useful enough to provide a few alternate layouts based on screen orientation, but it would be nice to get further feedback from fulltime Android developers about it. Things like how useful it is in the real world with real, fragmented devire types seems hard to come by...
[1] http://developer.android.com/guide/topics/resources/resource...
There are really two types of fragmentation. The first is UI screen size, which isn't too hard to work with. The second, and uglier, is code fragmentation. This is where a piece of code might work totally differently on two separate platforms. Right now Android has a lot of the former, but it's looking like there's a lot of the latter to come.
What's most unfortunate is that it's not even bullshit -- they are actually adding real value! HTC's on-screen keyboard is better, and they add in some of the multitouch events that Google foolishly left out.