As an IT consultant, I have a lot of different responsibilities that I have to maintain. Not only do I have a plethora of emails and projects to handle simultaneously, but I also have meetings to attend, deadlines to be met, and networking to be done. Even though these tasks are quite manageable, being in IT makes it much more interesting as I spend more time speaking and networking with persons across the globe than I actually do w/ persons who are local in Tennessee. On top of all of this, I also have the responsibility to my clients (and to myself) of continuing my education so that I can deliver the best solutions possible. This results in me spending ALOT of energy reading blogs, watching screencasts, and participating in discussions online. Taking all of these things into consideration, I have very little time to waste. In fact, I often feel like running in circles in my house screaming, "What to do now, what to do now?" - because that always gets things done faster, ;).
So, the point of the opening rant is to basically say that I am in need of a device that will allow me to keep in touch, keep my information in line, keep myself up to date, and also have enough gadgetry that I can create custom solutions so that I can further increase productivity. To be totally frank, this is not cutting it:
About a couple of weeks ago, I made the decision to upgrade my phone to one that is able to handle everything that I need of it. Given the current selection of phones, I only had a few choices. For the sake of brevity (I am often accused of being wordy), I make a quick pro/con chart of each option.
Brief Disclaimer - I am comparing this according to my own criteria. You can find a plethora of comparisons of the products, which often devolve to cross-fire and flame wars. I try to make a pragmatic approach to these to see how they serve my needs. Due to this, you may find my comparisons somewhat incomplete as I tend to gloss over the "hot topics".
iPhone
| Pros: - *If* I made an application, I could sell it for $$ with little pain.
- Good Coverage Area
- Cheaper monthly plan than Verizon's Blackberry plans.
- Has good glitter factor (not a big deal to me)
- Wifi support!
Cons: - Not an application architecture that I would love to dev for.
- Very closed system. It can be jailbroken, but that is a pain to maintain.
- Very closed hardware architecture. Welded battery FTL.
|
The Storm
| Pros: - It is a Verizon Phone - I am currently a Verizon user.
- Verizon has the BEST coverage area in TN (and many other places).
- Open API in .Net. As a .Net programmer, this is cool!
- Has decent application base (nothing compared to the iPhone though
Cons: - It is a generation 1 endeavor. Scary.
- No wifi!! What were they thinking?
- Not as smooth UX as iPhone (but still pretty darn good)
- Have to pay BB plan. Current phone plan + 30 bucks. Ouch!
|
So, after careful consideration, I found both phones to be very similar and both an acceptable solution. They both have nice web browsers, widgets for RSS feeds, internal calendars, ability to do instant messaging, twitter, and sms, email support, etc. After carefully considering these options, I finally decided that I would go w/ a Storm - mainly due to the fact that it is Verizon, has better coverage, and the API thing.
On the day before the storm released, I was all happy w/ my decision and then Gabe had to throw a wrench in the whole thing. After listing my thoughts to him, Gabe said, "Check out the G1." What!?!? Another phone option? Noooooo... So here we go:
The Android (as represented by T-Mobile's G1)
| Pros: - Based on an open source phone architecture. I can completely 100% modify anything about the phone (even the core menus / functionality).
- API is in Java - I am not a Java guy, but I am a C# guy. This, at least, gives me a better edge when starting to develop. Plus, I can pester Gabe for Java stuff, lol.
- Application base that is quickly growing.
- T-Mobile's plans are cheap! Dirt cheap as compared to the Verizon and AT$T
- Hardware is open, but the OS is not limited to 1 phone. Might see future phones / carriers support the Android.
- Its friggin' Google! <3 Google! (Don't get mad M$, I like you too :) )
Cons: - T-Mobile does not have a G3 network in K-town.
- T-Mobile had absolutely dismal coverage area in TN - period.
- T-Mobile is does not have a corporate office in K-town. Have to deal w/ "hot dog" vendors in malls.
- T-Mobile is the only carrier that has the Android.
- Notice a trend here? Adding another T-Mobile con just for being T-Mobile.
|
So, after another agonizing round of careful consideration, I found that the Android would have been my choice, hands down, if it were not for the fact that T-Mobile is so craptactular in this area. I even went so far as to call their corporate office to ask what their plans were in our area. They stated that they were planning to build a corporate office in K-town and that they would have G3 support within "a year or so". Finally, I called one of the "hot dog" vendors and, typically, they did not know what was going on, did not have a display model of the G1 phone, were not very helpful, and left me w/ a feeling of insecurity regarding overall their intelligence. :) Man! I am excited about the Android!
In the end, I ended up choosing the Storm, but with reluctance. I am buying the Storm, but I plan on watching the Android very closely. Within a year or more, if T-Mobile gets their act together or if Google can scrape some contracts w/ other carriers, I am going to jump ship and become an Android adopter. I sincerely felt that it is the best option, but just not feasible in our area for the next few years. Am I being wasteful by buying a Storm, even though I plan on moving to somewhere else in the future? I don't think so. Realistically, I replace my phone about once every 2 years or so. If it provides the kind of service I am hoping, I will be able to more than make up the cost of the phone.
So, big surprise, I am the owner of the Storm (even though have not gotten mine in the mail yet). In regards to this conclusion, Gabe had come comments regarding the outcome of my internal debate.
Gabe @nathanblevins did you get your storm yet?
Nathan @Gabe Nope, but I plan on blogging about the decision soon.
Gabe @nathanblevins lol, I wait with baited breath.
Nathan @Gabe Your sarcasm cuts deeply, sir. ;)
Gabe @nathanblevins not sarcastic at all, i really am curious, though since i can't see you changing your mind at the last second... it'll be like reading a book you know the ending to. . . Though I am open to surprises! ;-)
Cracking me up! Man, I hate to be predicable... ;)
So here I am, waiting for the impending Storm...
