Commentary

Thank Goodness Palm Canned The Foleo

Seriously. It was a disaster waiting to happen. Now the question is, can Palm refocus its team on creating the next-generation of smartphones?

Seriously. It was a disaster waiting to happen. Now the question is, can Palm refocus its team on creating the next-generation of smartphones?Palm needs a hit in a big way. While the aging lineup of Treos gathers moss, Palm's competitors have bested them at their own game with sleeker and sexier models. The Foleo, not even a smartphone but a laptop-esque smartphone accessory, was slated for market failure.

Said Palm CEO Ed Colligan in a prepared statement:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

In the course of the past several months, it has become clear that the right path for Palm is to offer a single, consistent user experience around this new platform design and a single focus for our platform development efforts. To that end, and after careful deliberation, I have decided to cancel the Foleo mobile companion product in its current configuration and focus all our energies on delivering our next generation platform and the first smartphones that will bring this platform to market. We will, of course, continue to deliver products in partnership with Microsoft on the Windows Mobile platform, but from our internal platform development perspective, we will focus on only one.

This is good news for Palm. Sure, it'll take a $10 million hit on its earnings, but that's a lot less than Palm stood to lose manufacturing and marketing the product.

Aside from killing the Foleo, it was good to hear Colligan admit that Palm needs to improve the user experience of its devices. This was a key point made by fellow Over the Air blogger Stephen Wellman a couple of weeks ago when he blogged about Engadget's open letter to Palm. Palm may have had a great user experience when the Treos first came out, but users are more sophisticated now and expect more from a world-class product.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links