HP/Palm Pre and webOS Review: Media (Music and Video)

This continues my review of the HP/Palm Pre and webOS.  Click below for the previous parts:

Part 1: Introduction and Hardware
Part 2: User Interface, Launcher, and Multitasking
Part 3: Synergy (Calendar and Contacts)
Part 4: Phone, Web, E-mail, and Messaging
Part 5: Camera, Photos, and Maps/Navigation

While the current version of webOS does an adequate job as a media player, I think it falls short of what it could, or should, have been.  A lot of commentators have noted that Apple’s success with the iPod means that the iPhone’s media capabilities should be expected to exceed those of their competitors, but I think there were opportunities for Palm to pull ahead here in many ways.  Instead, the media capabilities not only fall short of the iPhone, but, in some ways, also fails to match older competitors such as Windows Mobile and even the Palm OS.  I haven’t seen strong indications yet that HP is targeting these issues with webOS 2.0, although maybe there are partnerships to be announced in February.

The greatest opportunity would have come from countering Apple’s infamous adherence to a closed ecosystem by working to make WebOS  compatible with as many audio/video formats as possible.  Instead, Palm only included support for pretty much the same formats that Apple did, mainly variants on MP3 and AAC audio and H264 and MP4 video.  I think that Palm seriously missed the ball by not at least licensing the Windows Media formats from Microsoft and/or including support for common open-source codecs like Ogg Vorbis and Flac.

A big disadvantage on Palm’s side is a complete lack of support for any kind of protected formats at all.  That isn’t a huge deal for music, since most online stores have now gone to distributing unprotected files, but it greatly limits the available support for commercial movies and TV programs or for audiobooks.  I strongly think they HP should make every effort to get support for Audible.com audiobooks and for Windows Media protected video onto the platform as soon as possible.  In fact, I think seem support for protected video content will be absolutely essential for the tablet that they are expected to announce next week.

One of the biggest advantages Apple has is their tight integration with iTunes, which is now the largest music retailer in the US.  Palm wiselywebOS Amazon MP3 Store webOS Amazon MP3 Storepartnered with Apple’s most aggressive online competitor, Amazon.com, to include a nicely designed application for locating, purchasing, and downloading music.  I didn’t really expect to use this much, but I have actually ended up purchasing quite a bit of music this way.   It is nice to be able to purchase and very quickly start listening when I hear about some music of interest while away from home.  The music is the same quality as the downloads purchased from Amazon via the desktop and, since it is unprotected, you can easily transfer the tracks to a computer via the USB connection.

Possibly the single biggest miscalculation that Palm made early on with webOS was hacking synchronization compatibility with iTunes by having the phone attempt to impersonate an iPod.  This put Palm into a war with Apple, which they simply couldn’t win.  For a while, every update to iTunes intentionally broke this feature, with Palm having to quickly code a new hack into their OS updates.  The synchronization has now been broken for over a year and Palm finally gave up on the feature early.  The 1.4 update disabled the “Media Sync” option by default, requiring those still trying to sync with an older version of iTunes to go into the settings to re-enable it.  I’d be surprised if the feature is still present at all in Web OS 2.0.

That war with Apple was a monumental waste of time and resources on Palm’s part that left them with some damage to their reputation (the USB committee even cited them for using Apple’s USB ID) and a missing feature for their users.  It isn’t remotely surprising that Apple didn’t want Palm doing this and it created an ethical grey area at best.  Palm would have been much better off either partnering with a more willing maker of music management software or building their own synchronization tool, possibly making use of Apple’s published API’s for accessing the iTunes library.  Web OS still needs a viable media sync capability and hopefully HP is working on a sustainable solution.

Read More »

HP/Palm Pre and webOS Review: Camera, Photos, and Maps/Navigation

This continues my review of the HP/Palm Pre and webOS.  Click below for the previous parts:

Part 1: Introduction and Hardware
Part 2: User Interface, Launcher, and Multitasking
Part 3: Synergy (Calendar and Contacts)
Part 4: Phone, Web, E-mail, and Messaging


Walt Disney World Castle - Taken with Palm Pre

The Pre is the first cell phone that I have had where I have found the camera to take good enough pictures to be useful.  The phone has a 3-megapixel camera and a built-in flash, specs that fall a bit short of most newer phones but which were pretty good in 2009 and definitely better than any phone I had before.  While the flash makes it more usable indoors and in other low-light conditions than other cell phone cameras that I’ve had in the past, the camera is still better suited to photos taken in good lighting, particularly daylight shots outdoors.

Hollywood Bowl - Taken with Palm PreThe camera isn’t a substitute for a real dedicated digital camera, but it does take pretty acceptable photos under good conditions.  It has come in very handy for occasional photos taken when I don’t happen to have another camera along or when I want to immediately share a photo via Facebook or Twitter.  I think I took more photos with the Pre in the first couple months that I had it than I ever took with my previous phones.  The photos in this section were all taken using the Pre camera.

Admittedly, smartphone cameras have improved dramatically in the year and a half since the Pre was first released and most comparable phones have ones that are much better.  The Pre 2 increases the specs to a 5 megapixel camera and supposedly has some more advanced imaging than the Pre camera.  Palm/HP definitely does need a higher end phone with even more improvements to the camera, as well as a front-facing one for video conferencing.  The camera also lacks the touch to focus feature now included on the iPhone and many Android phones.

The camera application is pretty simple to use.  I have it on the top row of the first page of the launcher, allowing it to be accessed pretty quickly.  The controls available are a shutter button on the center bottom of the screen, a thumbnail photo to the left of the shutter to switch to the photo display application, and toggle on the right to switch the flash between on, off, and auto (based on a light sensor) modes and to switch to video recording.

Carousel Horse - Taken with Palm Pre

I do find that triggering the shutter using an on-screen control is a bit awkward and has taken some getting used to.  I would prefer a physical button for that and have actually found that my first instinct has some times been to hit the center button (which launches card view) instead.  If you don’t mind opening the slider, the shutter can be activated with the spacebar as well.  In some cases, that can be an easier way to take a picture.

Read More »

HP Palm Pre and webOS Review: Synergy (Calendar and Contacts)

This continues my review of the HP/Palm Pre and webOS.  Click below for the previous parts:

Part 1: Introduction and Hardware
Part 2: User Interface, Launcher, and Multitasking

webOS Contacts - Setup AccountsProbably the most innovative feature of WebOS is its ability to consolidate contacts and calendar data from multiple web-based sources, a feature that Palm branded as “Synergy”.  Currently, the OS can consolidate calendars from Google, Facebook, Yahoo, and Microsoft Exchange and contacts from those same services plus LinkedIn.  Calendar entries and contacts entered directly into the phone can be directed to any of those services or to an online Palm Profile that is created during the initial set-up of the phone.

This ability to manage personal data from multiple cloud-based sources is the killer application in WebOS and other platforms (especially Android) are already implementing similar features.  At this point, the lack of a similar feature is probably the most glaring omission in Apple’s iOS.  It is becoming increasingly uncommon for anyone to have all of their contacts and calendars in a single location and the ability to effectively organize and consolidate it all is becoming vital.  Since I’ve had the Pre, it has become my primary calendar and address book.  Even when I’m near a desktop or laptop computer, I know that I’m likely to find the most complete version of what I’m looking for on the phone.

webOS Calendar - Setup AccountsWhile it generally works reasonably well already, the feature is somewhat in the infant stage.  HP/Palm especially needs to expand it to pull data from a wider variety of sources.  They are still missing a few major services such as MSN and AOL.  Native support for more generic formats such as iCal would certainly be a big plus as well.  Adding synchronization of tasks and memos is also an obvious need that I’m pretty surprised that they have yet to address. WebOS 2.0 reportedly exposes more of Synergy in its public APIs, which should allow more services to implement their own synchronization.

I also strongly believe that HP/Palm should beef up their own Palm Profile service for those that might prefer not to use a 3rd party service for managing their personal information.  At the very least, they should implement the ability to view and manage data stored in the Palm Profile via the web.  Currently the data are only accessible on the phone itself.  There have also been reports of data loss from the Palm Profile when people have replaced or had to hard-reset their phones and this is something that is simply unacceptable with a cloud-based solution and must not continue.

One other shortcoming that is often cited is that there is no out-of-the-box solution for synchronizing with desktop applications for those that are still generally avoiding storing this kind of information in the cloud.  They do provide a tool for doing a one time transfer of data from Microsoft Outlook or the older Palm Desktop (used with the old Palm OS), but it does not establish an ongoing synchronization.  I don’t personally feel this is a bad decision, though.  There are already third-party solutions available to do this kind of synchronization (admittedly at an extra charge) and I think it probably is wiser for Palm to keep their own focus on the cloud-based approach, which I do think will be the preferred solution for most people.

CalendarPalm Pre - CalendarIn the calendar application, the default view is a combined one with the events from each source (Exchange, Google, Facebook, etc.) color coded.  In the settings, you can select the specific color to use for each source and can also have it remove specific calendars from the combined view.  From the main screen, it is also easy to switch to a filtered view that only shows events from any single source.

GwebOS Calendar - Monthly Viewoogle’s calendar supports multiple calendars on a single account and webOS treats each as a separate source with its own color-coding and option to display or not in the combined view.  Since Google offers the ability to subscribe to iCal or other types of calendar feeds, this provides a method to pull in events from many calendar systems that aren’t directly supported by Palm.  I use TripIt for travel planning and scheduling and was able to subscribe to its calendar feed via Google.

I have found that there are some quirks/bugs in the system, which I hope Palm will work out in time.  Sometimes updates made online to a calendar have taken several hours to show up on the Pre and, occasionally, never made it there at all.  This problem was particularly common when subscribing to an external calendar source in Google and I eventually ended up dropping the TripIt subscription in favor of manual imports.

Read More »

HP/Palm Pre and webOS Review: User Interface, Launcher and Multitasking

This continues my review of the HP/Palm Pre and webOS.  Click here for the introduction and review of the Pre hardware.

User Interface

Palm Pre - LauncherIt is difficult to ignore that the webOS user interface was pretty closely inspired by Apple’s iOS on the iPhone and other related devices.  Palm was the first to directly challenge Apple’s claimed exclusivity on a multi-touch gesture based interface on a handheld, which creates some obvious similarities between the interfaces of the two phones.  I’ve never owned an iPhone, but have become familiar with it because of my wife’s phone as well as some friends and co-workers that have them.  HTC also tried to emulate some of the iPhone-style gesture navigation with the Touch Pro, although it was greatly affected by the limitations of a resistive touch-screen, the lack of multi-touch, and the overall non touch-friendly design of Windows Mobile.

Like the iPhone, the Pre uses a capacitive touch-screen which relies on the conductivity of human skin.  This prevents it from detecting input when using a stylus or much of anything else other than a finger.  This type of touchscreen allows generally accurate finger-based selection with fairly high durability and easy support for multi-touch.  It also demands a user-interface that is designed for finger-based touch in essentially every aspect of its operation.  The physical keyboard on the Pre allows for more traditional data entry and the webOS design makes use of the keyboard to augment the touch screen for tasks such as precise cursor positioning and text selection.  I can’t fault Palm for copying Apple’s approach to touch navigation as the approach works well.  Scrolling, panning, and zooming are incredibly easy and intuitive.

Directly under the screen there is a touch-sensitive “gesture area” that is used for some additional navigation.  The most commonly used is a right to left swipe across this area that goes back to the previous screen.  This is used so frequently that the initial device set-up process when the phone is powered up for the first time includes a short practice session for it.  The other frequently used gesture is an upward swipe from the gesture area onto the screen, which opens the main application launcher, and there are a handful of other less frequently used gestures.  Tapping the gesture area is used to initiate cut/paste and other special operations.  The gesture area has been hailed as one of the more inventive elements of webOS, but I am actually a little torn about its value.  I’ve gotten used to it, but I’m not fully convinced that “back” and “home” buttons wouldn’t be simpler and more straightforward.

I also am not 100% sold on the completely stylus-free interface as I still find occasions where I would like to be able to select items with more precision.  In particular, corrections and insertions during text entry are tricky, although WebOS does alleviate this by allowing finger swipes to be used for linear cursor movement when the “orange” key on the keyboard is held down.  I have also sometimes wished for a stylus (or even responsiveness to fingernails) when selecting smaller links in web pages or emails or when playing some kinds of casual games.  Still, the combination of good predictive algorithms and easy to use zooming does minimize this as an issue.  Of course, the lack of a stylus eliminates the possibility of handwriting recognition or freehand note taking.

Any photo can be set as the background image on the phone (I currently use a photo of Sleeping Beauty Castle at Disneyland).  The photo to use can easily be selected from the Photos application.  The webOS approach of hiding the launcher when not in use makes this particularly useful as the background photo frequently is fully visible instead of being hidden by icons.  Even when the launcher is displayed, it is kept slightly translucent so that the background image is still slightly visible.

Read More »

HP/Palm Pre and webOS Review: Introduction and Hardware

Palm Pre

In October 2009, I purchased a Palm Pre smart phone on the Sprint network.  As a Sprint Premiere customer, I am eligible for upgrade pricing on new phones after the first year of the two-year contract, making now a good time to assess my experience with the Pre and webOS and whether or not to continue with it or look at a switch to Android or some other platform.  My review will be presented in several parts over the next several days.

With Hewlett-Packard (HP) recently completing their purchase of Palm, there is the expectation of new webOS devices on the horizon.  Late in 2010, the Pre 2 was announced along with the new 2.0 version of webOS.  More new phone models and a tablet are expected during the first half of 2011, with announcements likely to be made at a press event HP has scheduled for February 9th. The Pre 2 is just a moderate upgrade to the specifications,  but it does address a few of the nagging issues with the Pre.  The OS update is pretty substantial and does add some nice new features, although most of those features will eventually be available on my current Pre as well via a firmware update.

In the United States, the Pre 2 is currently only available in a costly unlocked GSM version, although a subsidized version on Verizon Wireless is expected soon.  Right now, it doesn’t look too likely that other carriers are going to rush to pick it up.  A new Sprint webOS phone could be announced later, but I may have to consider whether or not an upgraded Palm phone would justify changing carriers and paying the cost of the pro-rated early termination fee for the 2-year contract (or waiting until October to upgrade).  I’ve found Sprint’s coverage near me to be spotty, though, so this may be worth considering.

I’m going to go into much more detail about the pluses and minuses of the Pre and webOS over the rest of my review, but I’m going to also cut to the chase and give my current thinking right away.  At this point, my plan is to sit tight for the time being and find out what new phones HP/Palm announces over the early part of 2011.  I do believe that webOS has some strong advantages over the competition that I would hate to give up and I would like to give the company a chance to impress me on the hardware side.  Upgrading to the Pre 2 right away would even be pretty tempting if it were available on Sprint, but I’m kind of glad it isn’t as I might be happier with a more advanced model.

I should mention that actually started writing this review shortly after I purchased the phone and have worked on it periodically, adding new thoughts and observations as my experience with the phone has grown.  Eventually, it felt like it had gotten to be old news, so I set it aside without completing it or posting.  I feel that writing my review over more than a full year of use gives me a more meaningful perspective  than if I had published a first-impressions review shortly after I got the phone.

My History with Palm and Smartphones

I have a pretty long history with Palm devices, starting with my first PDA: a work-issued Palm V back in 2000.  Since then, I have owned a Palm VIIx (their first network-connected device), Palm Tungsten-W (a very early smartphone), Sony Clie UX-50 (Sony licensed Palm OS for PDAs at that time), a Palm Lifedrive (PDA with a 4GB hard drive) and a Treo 700P.  While a couple of those were among the worst designed models that Palm has put out, particularly the Tungsten-W and Lifedrive, I definitely have a strong affinity to Palm’s approach to the design of PDA/phones.

In late 2008, I became frustrated with the limitations of the badly aging Palm OS and switched to a high-end (at the time) Windows Mobile phone: the HTC Touch Pro.  While that phone was very powerful and feature rich, I pretty quickly became frustrated by the slow, clunky, and inconsistent user interface and the general instability of the OS whenever I tried to do anything overly complicated with it.  In addition, Apple’s iPhone had largely re-defined the user interface for a phone and I couldn’t help feeling that I was using a seriously outdated operating system, particularly after my wife got an iPhone allowing me to gain some more direct experience with it.  While many of the technical specs of the Touch Pro are still higher than the Pre, the Palm phone definitely feels much more modern and elegant.

I was interested in Palm’s webOS operating system as soon as they announced it at the Consumer Electronics Show in January 2009 and I followed the reviews and other coverage of the platform very closely, particularly after the official launch of the Pre in the early-summer.  I wasn’t eligible for a reasonably priced upgrade until October 1, which gave me a fair amount of time to monitor the progress of webOS and the Pre as well as its major competitors (particularly the Google-sponsored Android OS) before making a purchase decision.

Eventually, I realized that the webOS seemed to combine many of the good ideas that I’ve long found appealing about the iPhone, while addressing the biggest issues that have kept me from deciding to jump onto that bandwagon.  In particular, the inclusion of a physical keyboard, the generally more open approach to 3rd party development and the better support for multitasking were important advantages.  My research also indicated that the new OS still reflected some of the strengths that I had long associated with Palm, particularly a good balance between ease of use and flexibility/power as well as very innovative control over personal information management (PIM) data such as calendars and contacts.

Read More »

CompuServe Memories

On June 30th, America Online finally shut down the original CompuServe Information Service, which they had purchased in 1997.  While I haven’t really used the service for several years, this is still bittersweet news to me due to strong personal connections.  CompuServe was my first exposure to the concept of online computing back in the 1980s and my first professional job in the early 1990s.

My first computer experience was with a Radio Shack TRS-80 Model III that my father purchased in 1980 (when I was 10 years old).  Around that same time, Radio Shack made a deal with CompuServe to package and promote their service.  Under branding that Radio Shack called “Videotex”, they packaged CompuServe either with a dumb terminal or with terminal software sold for the TRS-80s.  My father bought a 300-baud modem and the Videotex package for the Model III, giving us our first look at connected computing.

My exposure to the features of CompuServe during this time was really just a taste as the service came with a pretty high hourly fee for use.  I mainly recall spending a little time watching over my father’s shoulder as he used it to access various news, weather, and information like that, although I recall that he generally preferred a competing service called The Source, which CompuServe eventually bought out and absorbed.  I also recall having a couple rare opportunities to spend an hour playing some of CompuServe’s primitive early online games.

Due to the hourly fees, I never spent any time in discussion boards or chat, instead getting early exposure to these via privately-run Bulletin Board Systems (BBSs) and, a few years later, with General Electric’s GEnie service, which was one of the first to offer discussion boards and a few other services at a fixed monthly fee instead of charging by the hour.  CompuServe was actually one of the last services to drop the hourly charges, which probably played a big role in their eventual decline.

After I graduated from college in 1991 with a degree in Computer Science and Engineering, CompuServe was one of the many technology companies to which I applied.  I ended up accepting a job with them as a junior engineer in their Entertainment Technology group, which focused on game products and the CB Simulator, which was their name for online chat.  I worked there for around 4 1/2 years, before I decided to move to California to pursue other opportunities in mid-1996.

The CompuServe headquarters was a campus in an industrial park located in the Columbus, Ohio suburb of Upper Arlington.  It consisted of two major buildings, the larger one (where I worked) housing the corporate business offices and the operations managing the consumer service.  The other building mainly housed their very lucrative network services division.  There was a nice employee cafeteria (The Oak Room), which was run by Marriot and an employee fitness center.
View Larger Map

The Oak Room had pretty decent food and I generally ate there a couple times a week.  They had a selection of standard grill items (burgers, chicken strips, etc.) that were available every day as well as a featured entree.  They would occasionally do prepared to order stir-fry or pasta that were immensely popular and would result in long lines during lunch hour.  I’d typically eat there on days that the entree sounded particularly good or when my schedule made it tough to leave the office for lunch.  When I did leave, there was a Wendy’s, a Pizza Hut, and a sandwich place across the street as well as numerous other restaurants that were a fairly easy drive.  The Oak Room also served as a location for larger meetings and employee gatherings.  I even remember just about everyone in the building gathering in there to watch the OJ Simpson verdict on a big-screen TV.

Read More »

Why I Don’t Have a Palm Pre Yet

June 6th was the launch date for the Palm Pre, the heavily hyped new smartphone from Palm and Sprint.  What I really want in a phone is something that matches the elegance and simplicity of the user interface on Apple’s iPhone, but still includes a physical keyboard and multitasking capabilities.  The Pre appears to be a very close fit, almost certainly much better than the Windows-mobile based HTC Touch Pro that I bought last year.

I definitely tend to be an early-adopter on new gadgets, so it certainly wouldn’t have been surprising if I had run out to buy a Pre last weekend.  In fact, I would have very much liked to have made that purchase.  Unfortunately, I’m already a Sprint customer and, as I mentioned earlier, I purchased a new phone last year.  Because of this, I am not currently eligible for upgrade pricing, which means that any phone purchased now would cost me considerably higher than the new or upgrade eligible customer pricing, which, of course, is the pricing that Sprint and Palm are advertising publicly.

I am, of course, under a 2-year contract with Sprint that was a necessary condition for the purchase of my last phone.  I completely recognize the validity and legality of that contract and that it is the underlying reason why I am not eligible for upgrading without a price penalty.  My purpose in this post is not to argue that my situation is somehow unfair or that I am being denied an entitlement.  I never had any expectation of being able to upgrade early and I don’t believe that there is anything unethical, much less illegal, about the system.

What I do question pretty strongly is whether or not the current business model used by the cell phone industry is a correct one in today’s marketplace.  Particularly since Apple has turned the smartphone into a much more mainstream product with the iPhone, the industry has entered a phase of extremely rapid growth and enhanced competition with frequent introduction of new models with desirable new features.  I strongly question whether customers are going to continue to be willing to accept a system that requires a 2 year wait between upgrades.

I had initially started thinking about this as subject for a blog post after getting into a Twitter discussion of it during the day of the Pre launch.  I got busy with other things and didn’t find time to start working on it until later.  In the meantime, this became a very hot subject generating a lot of coverage both in blogs and the mainstream press after Apple announced the third-generation version of the iPhone and AT&T revealed that the lower pricing would not be available to current iPhone owners that are still under contract.  This is a change from the approach taken with the last version of the iPhone, which was offered at the new-customer price to owners of the previous version, regardless of contract status.

The central idea behind current business model used by the cell phone industry is that the carriers subsidize a portion of the purchase price for the phone in exchange for the customer committing to a service contract, generally for 2 years.  If the customer chooses to switch carriers before the contract is up, he/she is obligated to pay a fairly substantial fee to buy out the contract.  Most carriers offer the customer the option of a smaller discount on an a new phone half way through the contract.  After the contract expires, the customer is generally eligible to again get the same subsidy offered to a new subscriber.

The contract system eliminates a lot of the need for carriers to expend much effort in customer retention, outside of the discounted phones offered at the end of the contract.  This likely saves the companies a lot of money, but is also almost certainly the biggest contributor to the industry’s reputation for poor customer service.  I have found that no matter which of the big cell phone carriers is mentioned, it doesn’t take long for someone to start telling stories about their horrible experiences.

It is in the best interest of the cellular carriers for most phones to have non-subsidized prices that are prohibitively high for most people since, otherwise, it is a safe bet that most people would forgo the contract.  This would make it much easier for customers to switch carriers at will and, thus, would greatly increase the cost and effort that the companies would have to expend towards retention.  I have little doubt that this would dramatically improve the quality of the customer experience, but it might or might not have a negative impact on profitability.

The big question is whether or not the non-subsidized prices really reflect the true cost of a cell phone or if they are kept artificially inflated by the cell phone manufacturers as a result of the subsidy-based sales model.  I admit that I have no direct knowledge, but my educated speculation is that the subsidized prices are probably more realistic.  The non-subsidized prices for phones (especially smartphones) simply seem way out of proportion with the pricing for other portable electronics.  In most cases, those prices are pretty close to what you would pay for a full-featured laptop computer and considerably higher than netbooks, stand-alone PDAs, or portable media players, any of which would seem more comparable technology.

The most obvious direct comparison would really be between the iPhone and the iPod Touch, which is basically an iPhone without the cellular radio or camera.  The pricing information for the 16GB version of the new iPhone 3GS has indicated that it costs $199 fully-subsidized (the price widely advertised), $399 for customers 1-year into their 2-year contract, or $599 un-subsidized.  The suggested retail price of the 16GB iPod Touch is $299 and it can be found in the $260-$275 range if you shop around.  I can certainly see where the added features of the iPhone would justify a higher price, but does it really make sense that they would double it?

In all fairness, my instinct looking at those numbers is that the $399 price offered after 1-year is probably the most realistic one.  While I suspect the price on the iPod Touch is also a bit inflated (it doesn’t really have direct competitors), it really does look like the $199 price probably brings in a pretty thin profit margin, if there is any at all.  The same is probably true with the similarly priced Palm Pre, although it does also have somewhat lighter specs, including only 8GB of memory. Even if the subsidies do push the prices down below the actual cost of the phone, I can still see justification for why the carriers might want to subsidize even for existing customers still under contract in order to prolong their contract and help to ensure loyalty.

I think that they might want to look to the satellite TV business as a possible example.  I’ve been a DirecTV customer for a number of years and they also use a system of contracts and subsidized equipment.  The big difference from the cellular business, though, is that DirecTV lets current customers upgrade their equipment (such as going to a DVR or hi-definition) at the fully subsidized price no matter how far they are into a contract.  The one catch is that doing so will reset their contractual start date to the date of the upgrade.  This helps to accommodate any need that the customer might have to move up to something better or different, while also pushing further back the date at which he/she might be able to switch to a competitor.

I do imagine that the cellular industry would probably prefer to stick with the current fairly customer-unfriendly system for as long as possible, but I do seem some recent signs that they may very well be changing their approach.  The recent publicity over AT&T’s prices for iPhone upgrades hasn’t been very good for them, even if they are pretty clearly within their rights.  A fan base as loyal as the more vocal iPhone owners, particularly when they are so willing to spend more money to make sure they have the latest and greatest, really does need to be cultivated and protected.  Policies that seem to directly target those loyal customers may not be in the company’s best interest, even if they appear to be the most financially prudent on the surface.

Another interesting development is Sprint’s recent introduction of the Sprint Premier loyalty program.  Customers that have achieved high longevity (10 years or more) or have one of the higher-end service plans (priced over $69.99/month, a fairly common price point for a smartphone with both a voice and data plan) are automatically enrolled in that program.  While the program offers a number of smaller benefits, the big one is that those customers are eligible for the fully-subsidized upgrade price at the end of the first year of a 2-year contract.  While Sprint’s recent issues with customer retention probably made this more necessary for them, it still is a pretty clear acknowledgement that higher-end customers are increasingly unwilling to wait 2 years between upgrades.

New Technology Blog

Technology (particularly computers) have been a big part of my life for many years.  I first became interested in computers at age 10 when my father purchased a Radio Shack TRS-80.  I eventually went into Computer Engineering as my career and have been something of a gadget collector all of my adult life.

For the most part, I have generally avoided writing posts that were too focused on technology for this blog.  I have a pretty good idea who my main readers are (most are friends or family) and I have a hunch that the interest level wouldn’t be overly high on most technology-related topics.  At the same time, it certainly is an interest and I often come across bits of technology news or various tech-related tips or experiences that I’d like to relate.  For this reason, I have maintained a second blog for quite a while for more technical posts.

When I first started that blog, it was very narrowly focused on Ultra-Mobile PCs (UMPCs).  I bought one of the earliest models released in that category and thought I’d have a lot to say as a bit of a pioneer in that area.  Eventually, I kind of started to run dry on things to post on that topic and expanded the subject to include all kinds of mobile technology.  Even that was a pretty limiting topic, though, and I eventually kind of abandoned that site as well.

I have now converted the blog into the generalized Bigbeaks Technology Blog.  My plan is to make it more of a traditional weblog with shorter, more frequent posts, frequently highlighting interesting news items or articles that I encounter.  I will also periodically post my personal discoveries or tips regarding technology and I’m sure I will also sometimes write reviews or longer essays as subjects come along that strike my interest.

Occasionally, I’m sure that there will be topics that are technology related (or at least tangentially so), but which still seem to be general interest enough for this blog as well.  In those cases, I probably will post on whichever blog seems to be the best fit and then put up a post on the other one linking back.  I suppose there may be rare occasions where I could choose to just cross-post to both as well.

New UMPC Blog

I have purchased a new Ultra-mobile PC (UMPC) and as an early adopter, I expect to have a lot to say about it. Because of this, I have created the new Bigbeaks Ultra-Mobile PC Blog.

This original blog will continue to be my place to post whatever comes to mind about any other topic, but I encourage those of you with interest in UMPCs to check out that new site. I have copied the two previously posted articles about UMPCs there, plus there is a new article with my first impressions of my TabletKiosk eo v7110 UMPC.

Palm’s Future Mobile Managers and the UMPC

Palm’s Future Mobile Managers and the UMPC
By Jeffrey Graebner

Since the recent announcement of Microsoft’s new standards and software for what they call an Ultra-mobile PC (UMPC), which I discussed in an earlier post, there has been a fair amount of speculation in the online Palm OS user community about what this means for the future of the Mobile Manager line. I touched on this topic a bit in my previous essay, but I thought the subject deserved a more lengthy discussion.

A recent editorial by Ed Hardy at 1src.com focused quite a bit on steps that Palm could take to make the Mobile Manager line more of a direct alternative to a UMPC. I think he is largely coming at this from the wrong angle. Instead of focusing on how to compete with the UMPC as a PDA, I think that Palm needs to understand that Microsoft’s announcement essentially validates the whole concept that Palm introduced with the Mobile Managers. Instead of trying to present the LifeDrive and its successors as alternatives to the UMPC, Palm should work to help the public understand that they are versions of the same idea. If Palm intends to continue with the Mobile Manager line, within a year or so I would expect them to be able to do essentially anything that a UMPC can do.

Read More »