Will Android Flavors Spoil the Platform?
rsmiller510 writes "Open source operating systems have a lot of upsides, but when you give cell phone makers and providers the power to customize the phones to whatever degree they like, it could end up confusing consumers and watering down the Android label."
I'm not a smartphone owner, not yet. I don't have a company paying my way for me and I'm not about to foot a $100/mo bill on my own. not yet and not with the current level of phones.
a few weeks after you buy a 'smartphone' some other model makes yours a POS. well, almost. how can anyone buy in that kind of market and retain sanity?
vendors are destroying the 'beauty' of the system. apple (I hate apple, btw) had it almost right when it controlled the carriers. the carriers are little children that run wild if not controlled. apple controlled them; android simply let them run even MORE wild.
google fucked this up. and I think its too late now, the market is SO fragmented its actually damaged. fanboys won't agree but who cares what they think; its the rest of us middle-guys who simply want something stable and something SUPPORTABLE for a few years. the throw-away model every few months is not do-able for me, for this pricepoint.
if there is ever a 3rd choice, I hope they learn from the 2 that 'came before'. apple model is too extreme but actually so is the android model. a middle ground needs to be there, really; and is not. we have the walled garden and the wild wild west where vendors can fark up YOUR phone and mostly get away with it.
I'm still on the sidelines and not willing to fund this insanity until it levels out.
--
"It is now safe to switch off your computer."
Not much more I can say. After developing for a year and a half by myself, it has gotten unmanageable. I can make an app that is polished and slick for the Droid, but the ratings get dragged down by other devices that it apparently doesn't run slick on.
As a single person I can't possibly manage all of the QA and customer service that all of these devices demand. It was fun while it lasted. Never developed for the iPhone but I can see how it might be a better experience.
The customizations many vendors tack on to Android suck (for the most part). Just leave Android alone and it works fine.
"I'm not a quack, I'm a mad scientist! There's a difference." - Dr. Cockroach
Three or four main distros each with three or four main desktop variants, each available in 64 bit, 32 bit, and who knows what else. To a newcomer, the choices are mind boggling.
When our name is on the back of your car, we're behind you all the way!
All it takes is a few vendors to drop the ball with bad implementations, or go out of business dropping support to create a bad association with Android. That's the real issue. Bad PR goes a lot further than good. At some point someone will put out a really terrible version that will in some respect hurt the label.
As a developer this is exactly the reason I've moved to iPhone development, and away from Java on mobile devices. Nokia, Samsung etc ruined it for themselves by introducing conflicting extensions and quirks to their platforms, along with expensive certification schemes in partnership with the carriers that made distribution as a small company or sole developer prohibitively expensive and time consuming. Apple smoothed this out no end with its single store and platform.
I'm no fanboy of Apple, or anyone else, but increased fragmentation, and the "embrace and extend" attitudes of phone manufacturers could well end up frustrating Android developers in much the same way.
Code, Hardware, stuff like that.