Android's "hardware specification openness" could be as much an inhibitor to platform advancement as it could be an enabler.
Back on Page 1 someone mentioned that Droid offers a higher resolution screen than the iPhone, which is true. It's also higher resolution than HTC's T1 and Hero Android phones and might be higher than Sony Ericcson's upcoming Android phone.
So if you are a game developer, what do you do? Do you create a game with high-resolution textures that take advantage of the Droid while making it impossible for T1, Hero, and SE customers to run the game, limiting your available sales opportunities to one model?
Or do you go with lower-resolution textures that allow you to target all four Android platforms to maximize your potential sales opportunities while delivering a "sub-par" experience on the Droid?
What you likely do not do is create two (or three or four) sets of textures, each tailored to the native resolution of each individual device. Doing so would allow you to target every platform, but it also drives up your development costs and increases the time necessary to delivery your product to market. And when you do deliver to market, there will be new Android phones available with different native resolutions you will need to go back and develop for.
Google is selectively choosing which hardware partners receive the latest advancements the Android software platform can support. HTC served as Google's primary partner to launch Android 1.0 and 1.5. Sony Ericcson is (or is one of) the primary partner(s) for 1.6, and yet they have not even released their phone before Google make Motorola's Droid the exclusive Android 2.0 phone. And 2.0 offers enough compelling advancements that the demand for Android 1.x phones from HTC, SE and other suppliers will likely plummet, which means they have to scrap their remaining stock or sell it at a loss just to clear inventory. Those companies will need to develop a new phone to entice Google to allow them to exclusively run 2.x in order to become relevant to consumers again, knowing that they are one "killer feature" away from being made irrelevant again.
Back on Page 1 someone mentioned that Droid offers a higher resolution screen than the iPhone, which is true. It's also higher resolution than HTC's T1 and Hero Android phones and might be higher than Sony Ericcson's upcoming Android phone.
So if you are a game developer, what do you do? Do you create a game with high-resolution textures that take advantage of the Droid while making it impossible for T1, Hero, and SE customers to run the game, limiting your available sales opportunities to one model?
Or do you go with lower-resolution textures that allow you to target all four Android platforms to maximize your potential sales opportunities while delivering a "sub-par" experience on the Droid?
What you likely do not do is create two (or three or four) sets of textures, each tailored to the native resolution of each individual device. Doing so would allow you to target every platform, but it also drives up your development costs and increases the time necessary to delivery your product to market. And when you do deliver to market, there will be new Android phones available with different native resolutions you will need to go back and develop for.
Google is selectively choosing which hardware partners receive the latest advancements the Android software platform can support. HTC served as Google's primary partner to launch Android 1.0 and 1.5. Sony Ericcson is (or is one of) the primary partner(s) for 1.6, and yet they have not even released their phone before Google make Motorola's Droid the exclusive Android 2.0 phone. And 2.0 offers enough compelling advancements that the demand for Android 1.x phones from HTC, SE and other suppliers will likely plummet, which means they have to scrap their remaining stock or sell it at a loss just to clear inventory. Those companies will need to develop a new phone to entice Google to allow them to exclusively run 2.x in order to become relevant to consumers again, knowing that they are one "killer feature" away from being made irrelevant again.