Tips and Tricks About Computers, Web Development, Linux, the Internet and the Like
Retorting An Extremely Biased View Against Android
Introduction
Those of you that have been following my blog for a while, know that I’m a big supporter of FOSS and Linux. It should come as no surprise then, that I have an Android phone. It’s not the best on the market by any means, it’s one of the first to appear on AT&T’s network but it gets the job done and I like it more than the iPhone (v2) I owned for 6 months. I’m not oblivious to the Appleverse, at my office, I have a Mac mini and an iPad. As a web architect, I need to make sure different operating systems can work from both a development and user viewpoint.
I’m also a bit of a console nerd, I prefer to automate as many tasks as I can. Apple’s terminal has come in handy at times but the BSD base and lack of a [good] package manager have left me yearning. That said, this is a blog post is more focused on the fragmented Android market and the points made by Marco Arment, who has recently claimed there is too much hardware choice for Androids. His bullet points are dripping with Mac bias and as a Google and Android fan, I’d like to weigh in on his “points”.
Breaking Down His Arguments
Accessory markets never fully develop. People really like cases for their phones, and if the iPhone has 300 cases for it including that gummy pink one they really like, and the Samsung Whocares XL only has a few drab OEM plastic things available, a nontrivial portion of the market will choose the iPhone on that reason alone.
There’s also more practical concerns: batteries, docks, speakers, and other useful accessories are usually phone-specific, and if the manufacturer (and the market) will only care about your phone for three months until the next minor revision comes out, your options will be very limited, both in the store and when you’re traveling and forgot something.
- “Arment”
This is a very trivial point because many Android devices use common ports and standards. Micro USB, micro SD, standard size audio jacks, etc. I’m able to charge my phone with any micro USB cable, even if it’s not the same phone or even device, anything from audio controllers to hardrives can use Micro USB.
An iPhone can only charge with a device from the Appleverse. An audio cable is only a few bucks from Radioshack or amazon.com if you don’t have one already and good stereos have audio ports. If you need to by another stereo just to dock your iPod or your phone, you’re not thinking rationally or hanging out in the wrong room.
There are so many variations in screen size, screen type, physical size, hardware sensors, hardware buttons, and computational performance between devices that developers, including Google itself, have a very hard time making great software for the platform.
I find the statement “Have a very hard time making great software for the platform” ignorant. This makes me think Marco hasn’t even used an Android because he’s apparently overlooked the navigation software, Google maps, Google Goggles, gmail and others.
My phone has a smaller screen, though I’d prefer a larger screen with a kickout keyboard. I don’t think the smaller screen has any major bugs with Google’s software and it’s running Android 2.1. I’m missing out on some features [, none that burden me] but holding out for a dual-core and hopefully a kickout keyboard.
Some people like choice. The buttons are pretty standard across the phone, I’ve seen different orders or positions but it’s pretty easy to recognize because they use similar iconography. Besides, doesn’t having this sort of choice allow consumers to need less accessories if the phone can serve a purpose as one device?
iPhone has one button, which is circular with a square in the center, if it doesn’t do what you want, then you’re either out of luck or need to buy an
Lets look at some Androids (click to enlarge images)





The manufacturers and carriers have very little incentive to maintain the software on devices that are still relatively new and under contract, because they want everyone buying the newest ones instead. We’re already seeing carriers and some manufacturers refusing to release new Android versions to handsets that were launched as recently as 6 months ago, even though most users bought them with 2-year contracts.
This will be moot soon enough anyway, the Android operating system is still fairly new, it’s popular enough amongst manufactures that it’s developing at a rapid pace. It’s not a surprise that carriers don’t want to push updates right away, they are still getting used to it. Android is running across a bunch of different hardware but because of intelligent software design, it’s able to do so. With proper organization of the code and more standard development across phones by companies or consortium, it will become a strong piece of software. Why do you think Linux and Apache are the backbone of many servers, and new open-source languages and software are thriving.
The number of iPhone users claiming insurance purposely breaking their phones to upgrade skyrocketed. Besides that, there are plenty of people willing to drop the cash on a new one. It’s not like Apple gives your old operating system a major upgrade (once) but oh wait, this is what you seem to expect from Android.
Flexibility isn’t well known in the Appleverse because their software only needs to run on very specific hardware. Apple products work best on Apple products. iTunes and I guess Safari (don’t kid yourself Steveo) on Windows increase their market share.
People hate choosing between similar things. The more choice we have at the time of purchase, the more stress we feel making the choice, and the less satisfied we feel afterward because we’re worried that we made the wrong choice.
But weren’t you just arguing that this was what was great about having a single phone design, a thriving accessory market?
Closing Thoughts
If the future battle is for content. Google has the most of it and will figure out ways to get content into its possession. Google is supporting Flash but has been on the forefront of HTML5 supported media since inception. They are setting themselves up to bring the internet towards their own video format, which was pieced together in a matter of days from existing standards when the h.264 vs ogg for HTML5 video debated first started months ago. Steve Jobs got upset that h.264, which his hardware decodes wasn’t chosen and a new format war began.
Don’t expect this change to happen overnight. Dropping flash right now would essentially break the web but as soon as Google can drop flash, it will. They’ve already converted all the youtube videos they can to other formats and now it’s standard when new videos are uploaded.
The pieces are coming together and Android is popping up to serve content in all sorts of unexpected places (nook, cable boxes). Remember, companies have been adopting Android for devices that don’t officially support it yet, these differences have begun to be abstracted as we see better support for tablets in Android 3.0.
This is not an accident and to argue that it’s going to be too different across devices of the future is like arguing against an OS such as Windows on a desktop versus a laptop versus a warship vs an ATM machine. Flexible software running across all different hardware expands the reach. This is something you will never get from Apple, who won’t even legally allow you to run OSX in a virtual machine, however, you can run other OSes inside OS X.
The Appleverse requires total submission, I could not turn on my iPhone or iPad without first connecting them to iTunes, there is no such requirement for Google. You don’t have to associate it with your Google account and you don’t have to give Google your information but if you don’t, functionality may be affected.
Your iPhone accessories won’t save you from the glass ceiling that is hardware dependent software. Arguing that you can jailbreak the phone for more features is admitting Apple is doing something wrong and furthermore, you’re making yourself more prone to an attack by installing software from a rouge app store.
Thomas Edison’s Direct Current was cool when he invented it but Alternating Current goes further and starts less fires.
Henry Ford was quoted saying “Any customer can have a car painted any color that he wants so long as it is black.”
| Print article | This entry was posted by Tyler Mulligan on January 14, 2011 at 11:11 pm, and is filed under Computers, Software. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |

about 1 year ago
I think you mean ‘biased’. A person has a bias, one *is* biased.
about 1 year ago
Thanks, I’ve corrected this.
about 1 year ago
Uhmm, but Android, at least for users who don’t make apps, isn’t very open at all. Variety, but open for them doesn’t really happen. For your discussion, and perspective at least, wouldn’t the Nokia N900 be an open solution that has more end-user benefit even without the polish of Android?
(will try to remember to come back here for your reply, feel free to poke via email/Twitter (arjwright) when you do reply)
about 1 year ago
I think the n900 is great in concept but I believe enough nokia has moved on with their merge with intel’s Moblin creating meego. Meego I think will do very well but I don’t know if they’ll have the coverage Android does. I’ve been able to find all the apps I needed or alternatives and as the market share slides towards Android, we’ll see more developers looking to monetize.
about 1 year ago
Great in concept? Its a finished product, am not sure what you mean there by concept. Maemo is still supported, and the N900 serves as the reference design for MeeGo – it will get a port of the first and most likely next after – releases of it. You speak of “coverage,” which I assume you mean licensee support – until the handset port is closer to release, I doubt you will hear manufacturers talk, and you definitely won’t hear carriers say much until device(s) are ready to ship. MeeGo (handset) is built to be carrier friendly, and those companies paying attention to that space aren’t entirely little fish.
In respect to monetization, I can understand. Developers move to platforms where they believe they can scratch an itch, and occasionally make a few bucks. Rovio put Angry Birds on the N900 for that reason, and its worked out well for them. Skype video was there for similar reasons, and there’s still not as elegant a contacts/IM/messaging plugin-solution as what Maemo has done. To that end, your reasons for being with Android vs Maemo are confusing to me – it matches hardware and software points you raise, with the sole exception of device variation.
My reasons for the suggestion had to do with your leanings towards those things “open source” that you noted. Maemo doesn’t run into the carrier-control issues that Android does (until you root it), and it has both hardware and software open sourcing – which makes sense for the developer looking to push a bit.
about 1 year ago
Hmmm. Your writing is OK, but your reading comprehension stinks.
Youn can’t even get the guy’s name right !
about 1 year ago
I spelled his name wrong once, I have fixed it. Thanks for looking out.
about 1 year ago
Nice try, but your many grammatical errors don’t cover up the fact that you contradict yourself on just about every point you attempt to make.
about 1 year ago
Can you please elaborate?
about 1 year ago
Wow.
You should be a politician. You never actually answer any questions, just divert the topic elsewhere.
I’m am a developer.
I do develop for both iPhone and Android.
I can say without question that Android has some major drawbacks compared to iOS.
- Having a myriad of screen sizes does make it harder to develop for.
- Having a myriad of “app stores” makes it harder to reach all users.
- Carriers DO NOT support the latest Android OS.
This doesn’t necessarily make Android worse for consumers (yet), but it is definitely worse for developers.
about 1 year ago
“- Having a myriad of screen sizes does make it harder to develop for.”
Like this has never been a problem in personal computing? The solution has been and always will be to write more flexible code. Obviously developing for one screen size and set of hardware is easier but I’m arguing that limits a users option. There is, for example, no iPhone with a kick-out keyboard.
“- Having a myriad of “app stores” makes it harder to reach all users.”
Most “consumers” will be using the official app store, unless their carrier or device is trying to force them to use something else. Look up amazon reviews for tablets (pre-honeycomb) that try this and you’ll see a bunch of pissed off consumers that are figuring out ways to install google’s App Market. I understand your point but I don’t think it’s enough of an argument yet. If amazon had a market just as popular as google’s, then it would have more validity.
“- Carriers DO NOT support the latest Android OS.”
This is bound to change in the future at least within a limited scope. There are phones you can upgrade yourself, such as Google’s Nexus. As I explained in my post, Android got too popular too quick and as a developer, I’m sure you can admit what it’s established in the time frame is impressive.