Here is just the latest example of real developers debunking the fragmentation myth
Myth #5: Android fragmentation is a nightmare
They develop in Unity3D and had almost zero problems. Of 1970 devices they only had trouble with 3 devices. 2 of which were a market issue they couldn't work around but that were solved by a Google Play update so they only had to make a special workaround for 1 device that had a GPU driver issue
I'm not a developer, and I'm betting you aren't either. I'll take real words from real developers in this instance.
you know, what the app does is also paramount to how fragmentation will affect something. Some types of programs won't have any issue with ease. But others, its a big issue, especially ones that rely on the latest encryption and copy protection stuff, as well as fully locked down customized programing like all DIRECTV apps require. Add in streaming type stuff and voice recognition, and its a whole lot different than a calendar or game, etc..
DIRECTV isn't going to have a hundred people, developing apps for android, it doesn't make business since for them to do that, that's not their bread and butter. Netflix on the other hand, I'd be surprised if they didn't have more people than TiVo does working on their apps, that's their bred and butter. Can't remember where, but i read an article somewhere that netflix had something like well over 100 different android devices in a lab to test as they where updating apps and such and you can imagine how many people they would have had to do that at one time. Its unrealistic to think all companies would spend the money to do that, especially if its not at all their primary directive.
Android is far more resource consuming to program for overall. Period.