It's a long article, but well worth the read (it has extensive references to back up its claims) if you do any type of development on smartphones (like we do here at The Corporation). It's mostly about how bad garbage collection is on embedded systems yet how everybody is trying to use a garbage collected langauge on embedded systems (said embedded systems being smart phones).
Some of the platforms are themselves economically untractable for smaller teams. Android is a prime example of that; even if we skip over the overengineering of the native API, the documentation is simply useless. The odds of having a hundred monkeys produce something on the same level of coherence and legibility as the Android API documentation by typing random letters on a hundred keyboards are so high, Google should consider hiring their local zoo for tech writing consultance.
(Although from some of the comments heard at The Ft. Lauderdale Office of The Corporation, the term “overengineering” in reference to Android is an oxymoron.)