December 13, 2009

NPR on the NRI

An interesting piece produced by NPR about the change in the portrayal of the NRI (Non-Resident Indian) over the ages in the Indian Cinema. An interview with WNYC Reporter Arun Venugopal.

Love the ability to embed NPR content.

September 08, 2009

Connectivity - Part III

The third milestone in my love for mobile connectivity, happened shortly after I bought my second phone. It was work that demanded I have no personal time and took steps to get me a Blackberry.

The Blackberry turned out to be a very different being, in comparison with my current phones. Everything about it screamed business - no frills; just a steady solid performer. It had everything I wanted to get work done, nothing that would make me buy one for myself. But it was the company that was paying for it, so my decision making process consisted of little more than asking a colleague which handset he recommended.

Thus I came to be in possession of my new Blackberry Bold. The feature list was pretty impressive, not to mention a paid for, always online 3G connectivity. Completing my enterprise activation was a breeze, and within time I had replicated my email and calendar on the perfectly usable mobile device.

The keyboard took a little getting used to. Realizing the power of being fully connected took a bit longer. But somewhere between checking the location of my next meeting without needing my laptop and being able to reply to quick emails at the extremes of each day, I realized something strange - I was no longer fascinated by the new device. In comparison with the time I spent configuring and personalizing my earlier phones - the customizations to my Blackberry were close to nil.

At the beginning I attributed this to my trivial approach to selecting it. But that wasn't it. What had changed was me and my attitude towards connectivity. Full mobile capability had quickly become a means to an end. With abundance came transparency - the Blackberry bold held little fascination beyond the emails it carried and the meetings it reminded me of.

I was no longer a connectivity virgin.

August 16, 2009

Connectivity - Part II

So, after about 5 years the phone - which was probably pretty advanced at the time of its purchase - was woefully antiquated. Not to mention the rough and tumble of time severely tested the paint, plastic and the buttons on the phone. It was time to get into the market for a new phone - and boy was it a revelation. All the time that I had not really paid attention to phone market, a number of new things happened - including the iPhone. But eventually I settled on my new Nokia 5800.

As I worked through the pros and cons of the phone, what struck me most was the extent to which my wants and needs from a phone had changed in the last five years. WAP an not an acceptable speed to browse. Browsing websites no longer meant struggling through text extracted by a lynx-lookalike; full color depiction of sites was expected. Email on phone completed with regular desktop clients in terms of capabilities and features. And having an always accessible device meant newer and more powerful applications. But instead of being overwhelmed, a missing accelerometer could be the reasons for rejecting a phone.

Beyond the physical capabilities, what struck me most was the ability to stay fully connected all the time. As soon as I acquired my phone, I linked my personal email accounts to the built-in email client, linked it up to my WiFi and was catching up on email with friends. The fact that this phone was able to connect to a wireless network, which about a couple of years ago, I couldn't find enough desktop software to support was mind-blowing. In addition, the phone also came with an in-built Global Positioning chip that spoke directly to satellites tearing across space fourteen thousand kilometers away.

And the thing weighed a tad more than a hundred grams or three and a half ounces.

The first mobile phone weighed in at 28 ounces, not including its antenna and only barely made phone calls.

In my mind this was my second generation of the mobile phone. My first phone showed me how to make phone calls, and use a smattering of other services. This one however was a more mature attempt at connectivity. However, I hadn't signed up for the ultimate of connectivity - an always-on network connection. And that would by the third time charm.

June 27, 2009

Connectivity - Part I

My first phone was bought back in late 2003. It was a Sony Ericsson T610. I remember this clearly, because I was among the last of my friends to purchase a phone. By the time we joined the productive workforce, mobile phones were no longer a luxury. Handset prices had been relentlessly pushed down by the glut of companies in the market, which was almost matched by the competition among the service providers. Before long, pretty much everyone I knew had a phone. And it became not only a connectivity imperative among friends, but became a requirement to keep in touch with team-mates and other business colleagues.

Everybody seemed to be doing it - so I held off - for seemed like eternity at the time, but was only about 9 months. Eventually I caved in. And when I went for a phone, I wanted to take one that had as many features as possible.

The T610 was pretty good for the time - It came with a tiny browser that you could use with WAP to trudge along the information superhighways. It ran JAVA applets - which was absolutely mind-blowing for me (and eventually led to the simple understanding that the phone was nothing more than a different avatar of the computer). And it came with a tiny camera that took 320 by 240 grainy excuses for pictures.

But I was ecstatic. I used every excuse to go online and check movie timings, even if no one else seemed remotely interested in going to a movie. I photographed and cataloged various events of my daily life now that I had a camera always at hand. I used an open source program to connect the phone to my laptop and use it as a mobile router (on WAP). I bought a terminator dongle online to flash the phone to the latest firmware (something that was pretty difficult at the time, requiring special hardware - the aforementioned termninator dongle). I backed up the files, restored them, backed them up again. I built by own ringtone (from the soundtrack of the game Blood)

Looking back, the phone did not do much, but it seemed at the time there was no limits to its capabilities. As it trudged along on WAP, I never stopped being amazed that the phone talked the same networking language as the old world mainframe behemoths - TCP/IP. When it took those tiny, barely recognizable pictures using the built-in camera, it always surprised me that they managed to squeeze a camera in there. I never saw it as the little engine that could, but I was pleasantly surprised that there was an engine in there to begin with.

I ended up using the phone for about 5 years. In the time I traveled across the globe; changed phone numbers at least 5 times; switched SIM cards every few months and generally pushed it beyond its limits. Eventually it's joystick started to give way, a few buttons began developing tantrums and no amount of dis-assembly to clean it helped. It was time for a change.

June 09, 2009

Cable indescretion

I normally am not much of a pointing-out-mistakes kind of guy. But I figure, it is not that bad if it includes a bit of humor.

So this other day I was looking up cable companies in Wisconsin. This site helpfully popped up claiming to tell me why cable was better, by pointing out the differences between cable and the dish. Which it did, helpfully pointing out that the cable is quite indiscreet.

I am sure they were thinking discreet, but unfortunately they let the cat out of the bag instead.

June 02, 2009

Google Wave

WOW. If you have an hour and 20 minutes at some point, this is a must see. The Wave is Google's ambitious replacement of the email, instant message, tweet, blog and pretty much every other means of communication and collaboration currently available. But Google's approach to do this is not by providing yet another replacement, but by linking to these means of communication and extending them transparently.

At its heart, the Google Wave is email done right. Updating the current paradigm of point to point communication bursts offered by email, Google Wave offers a centralized client-server real-time collaborative alternative. What this means is that email is no longer delivered to your Inbox. Instead, your Inbox is a sort of a window into a central location, that essentially hosts a dynamic, ever changing web page which is your email. As people contribute to this web page - called the Wave, the client (in this case a HTML 5 compliant browser) automatically updates itself to reflect a common shared view.

If that is all that Google Wave was, then it would potentially have ended up as an optional Google Labs widget for Gmail. Instead, the Wave team took this further. They added real time - character by character refreshes; provided drag and drop functionality for rich media like photos and videos; enabled collaborative edit features for all content; and provided a means for existing communication mechanisms to interact with the content and updates. Suddenly the Wave seems much more than just a handy email gadget. Instead, it is a new way to think about communicating, sharing and collaborating.

The best part about Wave is that it forces you to think differently about communicating, by providing fundamentally different tools and mechanisms. A particularly enlightening moment in the presentation is when an old Wave was dug up where participants initially began communicating serially like an email, and realized mid-way through the process, that there was a potentially more productive way of continuing the same conversation through the editing features provided in the tool. It is this ability to simultaneously apply two diametrically different paradigms, that is the real potential for Wave. Users will no longer have to choose to learn a new paradigm - instead they can choose to stay the same, and wean off at their own pace.

The second major feature has to be its extensibility. The opening remarks encapsulated Google's approach to Wave - as a Product, Platform and Protocol. True to looking at it as a protocol, Wave developers seemed to have incorporated several real-world requirements into it. One example that sticks out is the ability for multiple Wave implementation to keep each other abreast only of updates that they really 'need to know'. Such an approach reflects today's Legal discovery requirements really well, and demonstrates Google's commitment to making this a broadly acceptable protocol.

The potential issues that Google will face in trying to establish a Wave based communication platform will probably not be technical to Wave at all. Google Wave assumes that ubiquitous connectivity, which seems to be the direction they have been driving with all their offerings. Of course, the Wave is going to use HTML 5's cache functionality to provide offline usage, but connectivity is still going to be critical in Wave's acceptance. HTML 5 brings another item of resistance for Wave's acceptance. It was only recently that Firefox finally overtook IE6 in terms of usage. Browser adoption has and will never be as cutting edge as Google will want it to be. Not having a HTML 5 compliant browser will effect Wave's adoption.

The second issue will be user acceptance. People have gotten used to email in the traditional sense. For the vast majority, thinking in terms of email is as far of a change as they can fathom. Forcing a truly dynamic paradigm upon them, may not be very successful.

The third issue is corporate acceptance. Large scale user and technical acceptance of new technology has always been tied to acceptance in the corporate world. Your company pays for you to learn something new, like say email, and you then take it up on your own. Wave offers collaboration aimed at smaller, widely dispersed teams. Unless companies are convinced about the benefits of Wave-ifying their email or IM, it may end up remaining just a geek's toy.

June 01, 2009

But Its Not Google - more Search News

BING is the new name for Microsoft's search, formerly part of their LIVE suite of services. This seems to be a good few months for search. Just a few weeks ago we had the inauguration of Wolfram Alpha, and now the Bing.

Microsoft purportedly was very focused on verb-ifying their new offering and therefore had to go with the 'ing' ending. But Bing? As Chandler would say, Bing is Gaelic for 'Thy turkey is done'.

Bing has been live for a while, and it is not really all that bad. My bone of contention with its predecessor, Live search, was the super-heavy pages used to display results, and not so much the quality of the searches themselves. That seems to have changed with Bing. The pages seem quick. Not much of a fan of the changing main page background, but maybe that is just a matter of getting used to it. Of course, if you want to see the previous photos, you have to install Silverlight.

I guess for me, that is what makes Microsoft so annoying. It is like a car salesman that just wouldn't give up. It is always a matter of, 'I will give you this if you want that'. Microsoft properties online seem to acutely make you aware that you are a guest and therefore need to mind your manners and clicks. The constant struggle for one-up-manship reminds one of a petulant child, unhappy about the attention being showered on younger sibling Google.

One more matter of annoyance before I move on. This one specific to Bing. I don't think I am much of a fan of location assumptions being made by the software and then filtering my results without really letting me know about it. Seeing local search results surreptitiously is almost like those sleazy ads one sees online, from ladies starved of physical affection who magically know where you live and want to make a tryst with you. I may be using a proxy - did Bing think of that? Filtering my results for Indianapolis, Indiana when I am not even in the same state, isn't smart as much as it is annoying.

Bing seeks to bring travel into the search engine. As an example, they trot out the ability to book flights to Hawaii. Apparently, that is all there is to it. Try booking a flight to Milwaukee, and you are back to Expedia or Travelocity. So maybe, Hawaii wasn't so much as a feature, as it was a demo. Maybe we need Silverlight to be able to book tickets everywhere else.

Overall the search is in there somewhere. The interface is definitely better, and worth checking out. It has a few new demos of potential new features to come. Otherwise, it is pretty much same old, same old.

May 18, 2009

Wolfram Alpha live

It has been a while since there has been something new on the search scene. There was one highly publicized, incomplete junk that came out a few months ago called cuil (pronounced cool). As the name portends, it was not. At all.

Anyway - a new site called Wolfram|Alpha (name rather unfortunate) - is the new kid on the block bringing forth a really different approach to search. Instead of searching through pages to suggest potentially relevant pages, WA tries to answer quantitative questions with just the answer. If you need to know the population of the world, you just ask 'world population' and you get the answer of 6.53 billion people.

Search is tough. Understanding and algorithmically analyzing human fuzzy interaction is inherently difficult. And WA is trying to do two things at once - understand the fuzzy world-wide-web and obtain facts from them. This has long been the goal of a semantic web, that is nowhere near reality today. At the same time WA is trying to understand user searches to generate quantitative queries that can then be applied to the data that it has collected earlier.

First impressions - WA seems to be doing an ok job on the two entity intersections. If you are looking for 'world + population', you are good. Or you are looking for 'India + mobile phones' you are good too. But trying to do an intersection of 'world + population + mobile phones' seems to trouble the search engine.

Another disappointing aspect is its inability to interpret date and time as a dimension to queries that seem to work well on 'today'. For example, searching for gold + price works well. But trying to search for gold + price + any date doesn't compute. This seems to work for dow jones + any date, but not for gold + price. See similarities to the third level intersection problem observed above?

What it seems to be doing a good job is on the roll-ups. Try searching for Asia + cellular phones. You not only get the total estimate for Asia, but you also get a list of all the countries with their estimated cellular phone populations. Pretty interesting eh?

All in all, WA looks like a good for an alpha. It seems to be able to do simple queries and roll-ups. Not really good with anything complex, not to mention numerous glitches in the UI of the site. Also interesting will be the response from rights holders to their data being used by the engine. Granted 'facts' do not fall under the purview of copyrights. But what would happen if, say, results from surveys started to be incorporated into search results? That is if WA can one day show you the percentage of all people in United States, having cell phones with AT&T service expressing satisfaction with their service in a survey. What will the survey owners think of that? What will AT&T think of that?

All in all, am really excited to see where this goes. Here to the semantic web, without having to work hard at it.

May 08, 2009

Talking to myself

When I re-started the blog a few days ago, one thing that played on my mind was the audience or lack of it. Over the last few years, I had been indoctrinated incessantly over the need to line up messages to an audience. Writing without an audience, as with this blog, seemed to be a hark to the old days and the old ways.

It took a bit of an effort to shake that feeling. What helped was the time I spent re-designing the website, hosting the blog on my domain, and learning a bit of XHTML, CSS and Javascript to jazz up the place. Nothing is better than a bit of creativity and mental challenge to drive clarity.

That is when I realized that the joy in what I did on this blog was for me and me alone. Writing is something I liked to do, and this provided a means for me to instinctively fulfill that urge. The website provided me with a means to basically bring together stuff I did over time to one place. There was a definite satisfaction in seeing a project come to fruition, the beats having to pander (!?) to an audience.

As Krishna says in the Bhagwad Gita:

To action alone hast thou a right and never at all to its fruits; let not the fruits of action be thy motive; neither let there be in thee any attachment to inaction.

It is the joy of writing and working on my website that is my biggest gain. And thus I go, talking to myself.

May 04, 2009

Nokia 5800 Free Applications

I discovered this new awesome javascript library called the jQuery. And that helped me put together something I had wanted to do for a long time. Check out the list of ~43 applications all of which are free for the Nokia 5800.

What did jQuery do? Well, check out the neat plugin for jQuery, that allows you to sort tables on the fly.

May 03, 2009

My 5800 - Top 10 faults

Nokia 5800

Nokia has done a very good job with the hardware requirements of the 5800. As noted in my earlier posts here and here, there are a number of things to love about the phone. But, as with anything else, there are always room for improvement, and here are some key opportunities. You will see that a number of examples are more interface and software related that could be modified in the future with an upgrade, which only speaks to the solidity of its specifications.

  • Video Acceleration: For all its capabilities, the phone definitely misses that zip 'on the toes' feel factor. It is not so much with the running of an application, as it is apparent with any screen changes. It could be games, switching orientation, changing between applications. There is a nasty delay, not bad enough for you to realize upfront, but just enough to slowly eat away at the quality of your interaction with the phone. What makes it worse is that that whole UI seems to be riddled with hacks to compensate, making interacting with the phone a bit of a hit-and-miss affair. Cramming in just that additional video acceleration, could have freed up resources just enough to make the phone feel a whole lot zippier.
  • Uncomfortable SIM slot: The Nokia 5800 has a unique SIM slot, that involves a notch that needs to be opened and the card slid in. However, to take an existing SIM out, there is no easy way. The back needs to come off, and the SIM forced out using one's nail or the stylus. For anyone who travels with the phone - it is definitely a major annoyance.
  • Thick-headed approach to text input: This is one of the biggest annoyances with the phone. There are a total of four different means to enter text into the phone - QWERTY (landscape), mini-QWERTY (portrait), T9 predictive and handwriting. And you can choose one and only one - changing orientation does not automatically choose an appropriate keyboard. Which means no matter how you are using the phone, when it comes to entering text, you need to change orientation to the method you had set before, and use the keyboard. Here are some potential alternatives - allow preferences for the portrait mode. Switch to a full QWERTY mode for landscape orientation and the preferred mode for portrait. And here is taking it further, be aware of the stylus being pulled out, and maybe switch to the handwriting mode.
  • Contacts bar: Of the two standby screens, one is a contacts bar. Really useful and comprehensive bringing in calls, SMS and email into one location. But, you can only have four friends. And everyone needs to have a picture. And if they have more than one numbers, hard luck - no way to specify (other than setting a default in contacts) which number you want to reach them at. So if your contact does not answer their mobile, tough luck. To try their apartment number, go rummaging through contacts, just like any other contact - rendering the contacts bar useless.
  • No predictive input for QWERTY: Soft keyboards are inaccurate. The Nokia soft full keyboards do not offer any predictive correction of near miss key strokes. They already have T9, this just has to be a different sort of one to many mapping, and having no support at all is a big miss.
  • Large buttons in landscape mode: The phone interface looks comical in landscape. The entire right side of the screen it taken up by big bulky soft keys, creating space for five buttons when applications typically have need for only two. Taking up twice the space required for buttons in the landscape mode is a egregious waste of the gorgeous screen real estate.
  • Browser: In spite of the intermittent tantrums of the bundled browser (where the program just shuts down in a huff), it does a reasonable job rendering the pages. However, the interface definitely needs a lot of tweaking before it is anywhere close to being done. Here are a few examples, there is a full screen browsing mode with no back button. The browser supports tabbed browsing, but you cannot open a second tab unless the website opens a new window. Copy paste doesn't work on web pages. Try to copy the address of your current page - you wouldn't believe the hacks required. This gives you a flavor of the idiosyncrasies of the browser.
  • Applications: S60 V5 breaks compatibility with S60 V3 which in itself has the FP1 and FP2 variants. What this means is that all applications need to be redone for compatibility, and there just aren't enough applications around the 5800 even 5 months after its launch. Scrounging for new applications seems to be the main activity of the blogger groups built around the phone. Nokia did put out some applications and is working on an app store, but they seriously run the risk of alienating developers for mobile platforms by fragmenting their development platforms this way.
  • Soft key for Menu: Every thing on the Nokia 5800 can be done via the touch-screen, except for one and only one thing. Opening the menu, which for some strange reason can only be accessed by using the white menu key. This wouldn't seem that much of an annoyance till you realize that the screen is designed for single-handed use, till the need to use this button makes it impossible. Not to mention, it fully breaks the UI consistency.
  • Clunky inconsistent UI design: Which brings us to the last point - the overall theme of many of the points above. More examples. Contacts uses a good-idea-in-theory-but-bad-in-practice interface where the buttons change based on your contacts and the previously pressed buttons. Something like the NeverLost interface on Hertz cars. That probably never went through a consistency and usability tollgate. Or consider the interface to add contacts on the contacts bar - looks suspiciously iPhoneque, while nothing else on the phone does. I am sure that never went through a consistency tollgate either. Overall the UI design looks like it has been built by engineers to demonstrate touch on the phone as opposed to a consistent user experience. That probably sums up what I think is the biggest fault with the phone.

There you go! That should serve as a good list for now. On the whole, the phone is not bad. But if this going to be the future of the touch platform for Nokia, then the platform needs a lot of work. And platform is not just on the phone (i.e., the user interface and the touch enabled S60 V5), but also the community and application universe developed around the application. By all accounts, the buzz around the 5800 has been phenomenal. Now the ball is in Nokia's court.

May 01, 2009

My 5800 - 12 reasons it's awesome

I have had my new Nokia 5800 for about 3 months now, having bought it in January 2009. During the period, it has gone through two firmware upgrades - first from v11.0.08 to v20.0.012, and the second one from v20.0.012 to v21.0.025. The first updated clocked in at about 133 MB and was available only via their NSU (Nokia Software Update) service the second one weighed in at only 4 MB and was available OTA (Over the Air).

Of the two, the second one seemed to have worked its magic on the phone, really making the interface more responsive, while the first one delivered the bulk of the enhancements. With two major upgrades in less than 3 months, it is ample proof that Nokia is indeed looking to the Nokia 5800 as a testbed to iron out any and all problems with its touch platform, before it start rolling out the big guns - the E series and the N series. That said, back to the question at hand - what really works with this phone.

  • Screen: This is probably the most gorgeous feature of the phone, that you see as soon as you switch the phone on. With a width the same as VGA and a height only a third short of VGA, the resolution is great. And there is no better way to experience this than by playing one of the bundled videos. (You may end up trying out the bundled Dark Knight trailer.)
  • Sound: The other think you will notice when you play the aforementioned trailer, is the sound. For a tiny set of speakers on a palm-sized phone, the sound is remarkably good. You can actually make out the different frequencies, and including, a very solid handling of base without the expected crackle.
  • Basic phone functions: The Nokia 5800 does a good job at doing what it is supposed to do - act like a phone. It is surprising how many smartphones are so choc-a-bloc with features, that somehow the basic functions of a phone take a back seat. Not with the 5800. Calling, maintaining connectivity, the speakerphone, contact management etc are all exactly as expected. Not having to sacrifice a phone to get a smartphone is a terrific feature of the 5800.
  • Size and Weight: At 109 grams, the phone is surprisingly light. And it fits beautifully in your palm, without being too wide or too narrow in depth. For me, the form factor of an iPhone did not seem as comfortable. The small details, like the recessed edge of the touch-screen, for example, adds a lot to handle of the phone. The build of the phone is pretty solid too. Even though it is built of plastic, there is very little of the plastic-y creaking during operation.
  • Storage: The 5800 comes bundled with a hot swappable 8GB Micro SD card. The hot swap means you do not need to switch the phone off to remove or add the card. Nokia, by bundling in a decent sized card, adds a lot to the bottom line of the deal.
  • Variety of Input methods: One of the advantages of a resistive touch-screen is that you can have input methods other than just the finger. A capacitive screen depends on the capacitive effect of the human finger to register a touch. So, it fails with a gloved hand, or a stylus. The 5800 on the other hand, comes with a stylus, a pluck (ex-guitar pick), finger, finger-nail etc. And taking the flexibility further, the phone comes with a variety of methods to input text - a full QWERTY keyboard, a mini-QWERTY, a T9 style touch input and even a stylus driven hand-writing recognition method.
  • Battery: One of the surprising aspects of the phone is its long battery life. One the days I ignore it, with just a couple of calls, the battery seems to last and last. With a little more strenuous usage, the phone easily lasts a couple of days on a single charge. Of course, no amount of batter-life is enough, but what the phone brings definitely counts as a plus.
  • Multi-tasking: A smart phone is supposed to do more than one thing, at the same time. With one of the three dedicated buttons dedicated to multitasking, it is not an after-thought. That said, the phone does struggle once a number of large applications are running in the background. But as long as you don't treat it like a laptop, it does a pretty good job.
  • Proximity & ambient light sensors: Small capabilities like this get lost sometimes. But the ability of the phone to set screen brightness automatically, switch off when held to the ear all add up to a solid user experience.
  • Other hardware capabilities: From a capabilities perspective, the Nokia 5800 is stuffed. In addition to everything else it comes with an FM Radio and twin cameras including front-facing camera for video calling. The primary camera comes with a short range flash, not for a room, but definitely great for those pub snapshots.
  • S60 platform experience: The Nokia 5800 is built on top of the S60 platform, version 5. The version 5 is the new touch enabled operating software, that includes sensor frameworks to deal with the other hardware capabilities of the phone. Having the legacy of the S60 platform, means the the basics are already in place. Phone, contacts, copy-paste, application control, basic UI characteristics are all tried and tested. Applications too follow a well established method to interact with the end users. While the 5800 sometimes feels like a clunky touch interface, the core of the system is in place and works like a charm.
  • Price: Has to be one of the best features of the phone. Retailing for under $400 (unlocked and unsubsidized) it is almost half the price of the iPhone and the Sony Ericsson XPERIA X1. Not having to jail-break anything or break warranty for flexibility is one of the best features of the phone.

In short, the biggest positives of the phone are its capabilities - the sheer hardware capabilities and the underlying S60 software. Which leaves the interface components and applications. Coming up in the next post - where the Nokia 5800 definitely needs a little help.

My Nokia 5800

The Nokia 5800 has been my primary phone for the last three months or so. My earlier phone, the Sony Ericsson T610, was getting old and was in need of a massive update (retirement). Being a Sony Ericsson user, the idea of switching to Nokia seemed pretty unimaginable to me at the time. But try as I might, there wasn't a SE phone that seemed to fit the bill. Having delayed my purchase of a smartphone, my list of requirements seemed to be growing all the time.

When I started looking for a phone in late 2007, my list of requirements was driven by the phones at the time, particularly, the iPhone. On a number of levels, the iPhone was almost a no-no from the beginning. I never saw myself buying an Apple product - I adore them, just don't agree with the approach and philosophy of the company. Anyways, driven partly by the iPhone and the other phones at the time, this was a list of parameters I had come up with for my first smartphone.

  • Touch screen: This was a must have for me. The way I saw it, the touch interface was going to be the standard interface philosophy soon, especially in mobile interfaces. Not to say the keyboard would be redundant, but the ability to interact with on-screen elements (for certain activities), without need for surrogates like cursors and element focus seemed to be the natural progression. And I wanted in on that. And for me, the physical keyboard was completely optional. Also, I was not sold on either the capacitive or the resistive touch screens. And so did not have particular loyalties to either camp.

  • Other sensors:Proximity, light and orientation sensors was definitely high on the list. I figured, I will have to carry a second device, that was more focused on communication and email - so why not focus on the fun factor with my personal phone. Lack of an orientation sensor was almost a definite deal-breaker. For a fun phone, that definitely had a big cool factor.

  • WLAN(WiFi): Was another must have. My plan was to have that as the primary means of getting data in and out of the phone. That would also save me a data-plan with my mobile carrier, which were not cheap to come by.

  • 3G: Was optional for me. The way I saw it, the 3G network wasn't ubiquitous enough to base my purchase on being able to use it. Especially given that I would be traveling and therefore not necessarily have 3G coverage all the time. The other side effect of this decision was that I did not have to worry about the NAM and Rest of the world 3G variants before I got my paws on my phone of choice.

  • Quad band: That said about 3G, it definitely had to be Quad band phone. Given, the same traveling nature - I did not want to get stuck with a phone that would not work in all my locations. My SE T610 did not do 850 MHz, and I had done my share of blaming the network (ATT) in public, secretly knowing that my phone was really to blame.

  • Flexibility and Freedom: This was one of the most important requirements. In two ways - firstly I did not want a branded and locked phone. I wanted the flexibility to be able to change SIM cards across different locations. (See need for traveling above). And secondly, I wanted to be able to install and uninstall applications the any way possible. I did not want either my carrier or my phone manufacturer to determine what I did with my phone. The other piece of freedom - access to the file system of the phone, without the need to install a clunky proprietary program.

  • Screen: QVGA (320 x 240) or better. Why? Coz the iPhone did QVGA.

  • Battery: At least 1200 mAh. Again, that did not really mean anything without a strong support from the device itself. I hoped for a regular usage of 2 to 3 days, and heavy use of a day before having to recharge.

  • Application ecosystem: Given that Apple was the only viable option dictated that this was not a necessity. But, as long as I was able to get a system that was open enough - It was a matter of time before people started trying to replicate the App Store.

  • Camera: This surprisingly was not really high on my list. Primarily because, I was yet to see a phone that did a tenth as good a job as my SLR. And there were physical reasons to it - a camera phone had the sensor the size of my pinky toenail. I did not expect to do any serious photography on my phone. On the off chance that I was to witness a UFO landing, I just hoped to have a video mode to create a grainy, shaky, unrecognizable account of the event.

  • Other connectivity (Physical & Bluetooth): Bluetooth was an expected minimum. Physical connectivity was not that important, as long as I had my WLAN access.

  • Browser with Flash: The browser had to be a full fledged web browser, running javascript and hopefully some form of Flash lite. Again, I was sick of my piddly little text-ey browser on my T610.

  • Memory: Expected a few gigs, but more importantly hope for one with an external card, which could be upgraded as and when I ran out of space on the phone itself. I have a tendency to run out of space - rather quickly.

The phones I was reviewing, at the time, were a wide variety. But they boiled down the the following:

It was neck and neck between these phones (though the Omnia went to the bottom of the pile pretty early) and it seemed just a matter of which price point I was comfortable with. As time went by, the Diamond seemed to slowly but surely rise to the top. XPeria was priced too high, and the screen of the Diamond beat that of the Touch hands down. Until the Nokia 5800 came along. If you look back at the list of requirements I had, you can see how well the 5800 stacks up. Next post - what I love about my 5800.

April 04, 2009


It has been almost three years since the last post. There is a reason for it, three years long. The bottom line is that for the last three years I had opted to let work take over all my time, choosing to put the rest of my life on hold. Virtually, pressing a super-pause button

That is all over now. Now it is time to move on, revive some of the old and start some more of the new. The world has changed tremendously in these last three years. I have too! Three years ago, blogging was fringe. Today it seems everyone does it. Three years ago, social networking was a fad. Today it is mainstream - threatening to make television a fad. A few years ago, doing a new post, meant an outside chance that I would get an audience. Today the audience seems stretched too thin.

Within that context, it seems I am back. To continue to make this a sort of thought-blog with ideas, rants and opinions across a wide-range of topics.

To kick it all off, we have a new blog name - as opposed to the old (That old name is now more or less defunct). It is now hosted on my own domain and website. And finally the website and the blog now share a new, common look and feel. The site now sports a new template, cleaner XHTML, css based design. The aim is, at some point, to achieve XHTML document compliance.

Here's to welcoming myself back!