Smartphone Wars

Wanting to buy a touch-screen smartphone, I asked the good people on Twitter for their help in choosing between an iPhone 4 and a Galaxy S 2 and was overwhelmed by the number of responses in favor for Android! There is no denying the kind of support / backing Android has managed to get over such a short period of time. Surely they must be doing something right. Was discussing this with boss-man and I got a smile as an answer. He had of course, yet again predicted this a while back.

So what is it that Android is doing so right, or Apple doing so wrong? The 2 very strong viewpoints I got were –
1. Android is much more configurable. It gives the power in the hands of the user. AND it’s cheaper! “Why throw away your money on iPhone when you can get something just as good much cheaper.”
2. While there is no denying the User Experience of the iPhone devices, a lot of people seem to find the Apple way of working rather restrictive. Even the store manager at a store in Saket said (and I paraphrase) – “iPhone does not give you the flexibility of sharing data. No bluetooth. You can only transfer data to your device using iTunes. And you can sync your device with only one pc at a time or risk losing all your data.”

The restrictiveness of the Apple-way also comes to the fore when we see their strong control over the app store and their continued resistance towards Flash (Adobe). App publishers like Playboy and Financial Times are now coming up with innovative ways of bypassing Apple’s restrictiveness – which may also be quite beneficial for the end users actually. I will try and cover that in another post though.

Lifehacker has also compared the 2 OS from the perspective of a ‘Power User’ in this post.

Apple vs Android (source: Lifehacker)

While the Apple vs Android debate may continue, Ideafarms is backing Android for now. We also welcome your opinion on the topic. Do let us know which phone / OS you prefer and why. You can also join the discussion here –>

[As for me, I might still end up getting an iPhone but that’s because it’s an old itch I have to scratch. Although I must admit I almost changed my mind 5 times while writing this post :D]

Enhanced by Zemanta

Published by


Officially known as the Creative Team Lead at Ideafarms, all things interactive catch her fancy. Claiming to be comfortably dumb, she is an avid tweeter. You can also reach out to her at @sunainak.

  • Nice post Sunaina. This is going to be an interesting debate while it lasts. I think it will be Android all the way for the reasons you highlight; no company can afford to display the kind of ‘excellence arrogance’ that’s becoming evident with Apple.

  • Anonymous

    Prefer iOS. Last week my friend & I tried out the HTC Desire/Desire HD/Wildfire Samsung Galaxy/Nexus S & all of them were laggy. I agree that Apple has a “my way or the highway approach” but that does translate into a good user experience!

    Yes my iPhone does not have flash & android does. But if you have to keep it turned off to prevent slow webpages where is the advantage?

    Yes my iPhone does not have “true” Multitasking, but it makes it through 1.5 days on a single charge. Unlike my friend’s HTC Desire which needs to be charged twice a day.

    my thoughts:

  • I’ll go with Android.
    Even though iphone gives u better user experience but 1. It is really costly 2. Every six months they launch a better version which makes your current version feel like its from stone-age and as for Android you can get them at reasonable prize and u can even even upgrade at a later stage  😀

    • Anonymous

      Yes I do agree that the Android phones are way cheaper than iPhones [even the Galaxy S2 is cheaper than the iPhone 4] & that is one area where Apple needs to work upon.

      Apple refreshes it’s lineup at regular intervals, usually yearly. So you have an entire with the best Apple has to offer. Unfortunately the same cannot be said for Android phones. A flagship phone from a handset manufacturer is launched every other month, eclipsing your new purchase.

  • Pingback: Neutralising Applethink()