On the road to Android's Froyo
For those who don't know, Google has used desert-based code names for the different Android versions. The names went from Cupcake to Donut to Eclair to Froyo and the next iteration is to be called Honeycomb. So here I am, running 2.1 (Eclair) and waiting on Froyo to be released in the next few days (I hope!).
The problem with Android is that it is taking the same path as Window Mobile. This is both good and bad. The fact that is open is good. The fact that carriers and phone makers can modify it is kind of bad. The customization becomes a problem when it causes delays in releases. If I could run a "vanilla-Froyo" (without rooting the phone), I'd probably have the new version running on my phone. The Nexus One has this pleasure because it was sold directly from Google and so OTA (over the air) updates were sent out very quickly. The rest of us have to live with customizations being tested out by all these people who are trying to create "the next best thing". The reality is that users will install what they like, not what is imposed. Almost all of the Samsung apps and widgets that came pre-installed (and that I cannot remove!!) are not better than what is available for free on the Android Market.
So why waste the users time, the phone makers money and time and delay Google's effort to roll-out updates when the out-of-the-box product is already excellent and users can just go to market to get what they need? It is very frustrating.
Now, we were promised a September release and the end of the month is near. Samsung Spain is reporting October release but UK still set for September. All of this confusion could be avoided if upgrades could be handled by Google alone. I'm not sure why Google is allowing this. Guess why Windows Mobile is extinct, too much hardware to support for too many versions of winMo. Microsoft is trying to fix this with the release of Windows Phone 7. Restricted hardware for a somewhat restricted operating system. Let's see how that goes. From the leaks flying around, they seem to be allowing customization layers also so I'm not sure what I think of it yet.
I think Google needs to be stricter with phone makers. Give them strict release dates and if they don't meet those dates, make them pay fines or something. It's Google's name that is paying the price in the end because people don't understand that it is not Google's fault, it is the phone maker's fault.
When I get Froyo on my phone, I'll write about how great or bad it is, until then, I can only wait.
The problem with Android is that it is taking the same path as Window Mobile. This is both good and bad. The fact that is open is good. The fact that carriers and phone makers can modify it is kind of bad. The customization becomes a problem when it causes delays in releases. If I could run a "vanilla-Froyo" (without rooting the phone), I'd probably have the new version running on my phone. The Nexus One has this pleasure because it was sold directly from Google and so OTA (over the air) updates were sent out very quickly. The rest of us have to live with customizations being tested out by all these people who are trying to create "the next best thing". The reality is that users will install what they like, not what is imposed. Almost all of the Samsung apps and widgets that came pre-installed (and that I cannot remove!!) are not better than what is available for free on the Android Market.
So why waste the users time, the phone makers money and time and delay Google's effort to roll-out updates when the out-of-the-box product is already excellent and users can just go to market to get what they need? It is very frustrating.
Now, we were promised a September release and the end of the month is near. Samsung Spain is reporting October release but UK still set for September. All of this confusion could be avoided if upgrades could be handled by Google alone. I'm not sure why Google is allowing this. Guess why Windows Mobile is extinct, too much hardware to support for too many versions of winMo. Microsoft is trying to fix this with the release of Windows Phone 7. Restricted hardware for a somewhat restricted operating system. Let's see how that goes. From the leaks flying around, they seem to be allowing customization layers also so I'm not sure what I think of it yet.
I think Google needs to be stricter with phone makers. Give them strict release dates and if they don't meet those dates, make them pay fines or something. It's Google's name that is paying the price in the end because people don't understand that it is not Google's fault, it is the phone maker's fault.
When I get Froyo on my phone, I'll write about how great or bad it is, until then, I can only wait.
Comments
Post a Comment