[bstar77]

If HTC wants to integrate these services into the core experience of their devices, then they are going to have to manipulate the android source in a substantial way that will contribute to the fragmentation issue. I think these manufacturers are expecting something out of android that it cannot deliver. These "kindle-esque" forks are going to be android's undoing.

We'll have to wait and see, but I think every major manufacturer is going to to try and build a platform/ecosystem similar to what Amazon and B&N have done.

[fluidcruft]

I actually don't think these high-level things are the fragmentation that matter. The fragmentation that causes delays are based on adapting the code to hardware. Things like releasing a phone with an 8MP camera, 720p recording and HDMI out running eclair and then having to rewrite that support the "AOSP-way" when froyo and gingerbread and ics finally add support for the same features to AOSP. That's the part of the "skin" that's the problem not things like widgets and more purely-software things. The challenge is that the market advances hardware faster than Google makes code available. The only way this can be resolved is if AOSP is developed in the open rather than behind closed doors. AOSP has a very strong case of NIH syndrome--but mostly because its impossible for them to share what the Nexus team is up to. Alternatively everyone could just build phones only based on Nexus chipsets and features, (but that's not possible either since the Nexus hardware is also kept under wraps during development and building new phones based on last years model isn't going to work in the market).