Lessons From the Fall of Palm

What went wrong?

Palm is now apparently prepping itself for a remainder sale, or new sugar daddy, or some other sort of deal that will change its current trajectory. I wish them well, and I hope they can remain independent and go on to accomplish great things in the future. But whatever happens, it's clear that the current incarnation of Palm has failed. Almost everyone I talk to in Silicon Valley is already speaking of the company in the past tense.

Most of the comments I've seen online blame the company's failure on the high marketing costs associated with selling hardware:

--Ed Snyder, an analyst with Charter Equity Research, told the New York Times: “They poured all their resources into developing a killer product. But they didn’t have the resources left to go to market.” (link)

--Engadget called Palm "a company that has more talent, history, and bright ideas than it has cash and customers." (link)

--Charlie Wolf of Needham & Company told Bloomberg: "It can't get scale. It doesn't have the resources to market the Palm OS and the Pre in a way that would break through the noise." (link)

--Even Palm CEO Jon Rubinstein blamed the problem on marketing challenges: "Palm webOS is recognized as a groundbreaking platform that enables one of the best smartphone experiences available today....However, driving broad consumer adoption of Palm products is taking longer than we anticipated." (link)

The quotes reflect the tech industry's stereotypical view of hardware businesses: They require huge marketing budgets, making them incredibly high-risk, high-cost investments. That's why you see thousands of software startups in Silicon Valley and only a handful of hardware ones.

I think that's nuts. Hardware companies like Pure Digital (maker of the Flip camera) succeeded with virtually no marketing budget. Why? Because they made appealing products that filled a particular customer need. If you do that, hardware is easy to market virally. I think the lesson from Palm's failure isn't "making hardware is dangerous," it's "lack of focus in a small hardware company is dangerous."

I don't want to turn this post into an anti-Palm diatribe. As I said, I hope they survive, and I have enormous respect for the people who work there. But in the spirit of helping everyone learn from Palm's situation, here are the five lessons I think we should all take away from Palm's struggles:


1. Understand what problem you're solving. I asked this question when the Pre was first announced, and I'll ask it again now: What compelling problem does the Pre solve for what customer? (link) It's easy to answer that for successful devices:

--BlackBerry = great e-mail on the go for mobile professionals

--iPhone = the best entertainment and browsing on the go (later extended to include apps)

--Flip = the easiest way to capture video and share it online

What's the short pitch for Pre? Go check the Palm website. As of April 18, it featured three different positionings right on the front page: "Social networking at its best," "Advanced 3D games," and "Work smarter, stay connected." So it's a business / social networking / gaming tool. For all of those millions of people who want to do serious business, 3D games, and Facebook posts all at once.

This isn't a recent problem. At the time of the Pre announcement, Palm advocates described it as a device for people who want better e-mail than the iPhone and better entertainment than the BlackBerry. The implication was that there's a big center to the smartphone market that's frustrated by the lack of a keyboard on an iPhone and the lack of a music player on BlackBerry. Re-read Jon Rubinstein's quote above: "webOS is recognized as a groundbreaking platform that enables one of the best smartphone experiences available today." The assumption there is that millions of customers are looking to buy a "smartphone experience," as opposed to a tool that solves a particular problem.

If that unsatisfied center existed, Pre would have sold like hotcakes.


2. Take care of your friends. When Elevation Partners took control of Palm, the company wasn't just a famous brand. It also had a fairly large base of loyal customers and developers who had stuck with the Treo through a lot of angst and adversity. The new Palm did very little to keep those people loyal. The developers weren't given any way to bridge their existing applications to the new OS. Faced with starting over on webOS or starting over on the much larger iPhone base, guess what they chose. And Palm, which once prided itself on simplicity, made the Treo to Pre migration process into the sort of marathon experience that we used to tease Microsoft about. Here are some of the instructions from Palm's own website (link):

Decide where you want to move your Calendar/Contacts

The Data Transfer Assistant moves your info out of the desktop organizer and onto your phone. From there, your phone sends the data to the web account of your choice.

Your choices: Google, Microsoft Exchange, or Yahoo!.
Need help deciding where your info should go?

Skip this step if you already have an online account where you want to move the info from your old desktop organizer.
Create an account for one of these web services:
Google

1. Go to Google.com: Create a Google account and set up a new account.
2. If you've never used Google Calendar, you'll need to sign in at least one time before proceeding. Go to google.com/calendar, and follow the login & activation steps until you see your calendar.

Microsoft Exchange for corporate users

Ask your IT Helpdesk for these four pieces of information.

* Incoming mail server name
* Domain name (if it's different from your incoming mail server name)
* Exchange username
* Exchange password

Yahoo! Calendar & Contacts

Contacts are transferred from Yahoo.com to the phone, but not from phone to Yahoo!

1. Go to Yahoo.com: Sign up for Yahoo! and create a new account.

Or back up your info to your online Palm profile

Ready to go - you already created an account when you set up your phone.

Set up the account on your phone

After creating an online account, add it to your phone. This ensures that your info moves correctly to the account.

1. On your phone, open Contacts.
2. Open the application menu and tap Preferences & Accounts.
3. Tap Add An Account and select the account you created above.
4. Enter the username and password for that account.

Sync your old device one last time

Skip this step if you do not have a previous Palm device.

To make sure you have the most up-to-date version of your info in Palm Desktop or standalone Outlook, synchronize your previous Palm device and your computer one last time.

Export your info using the Data Transfer Assistant

For fastest results, turn on Wi-Fi (if available) and plug in the charger before proceeding.

Download the tool: Data_Transfer_Assistant_1e.exe

After the download is complete, double-click Data_Transfer_Assistant_1e.exe in the location on your computer where you downloaded it.
Follow the onscreen instructions.
Note: When you connect the phone to your computer, some applications may launch automatically, moving the Data Transfer Assistant to the background. To return the Data Transfer Assistant to the foreground, click the Data Transfer Assistant icon on your computer's taskbar....

You can find some more discussion here.

This in itself wasn't a disaster. Any company has to set priorities, and Palm just didn't make the links to its legacy customers and developers a priority. But it meant Palm couldn't draw on a pool of friends to help it get sales off to a quick start. That put even more pressure on Pre to be a knockout hit from day one.


3. Move faster and slower. After the Elevation deal, Palm went through a very strange management transition. Jon Rubinstein was installed as Chairman and head of product development, Ed Colligan remained as CEO (so he was Jon's employee and boss at the same time), and Jeff Hawkins was supposed to remain as product guru. Palm said at the time that Jon would be the execution person and Jeff the visionary. "The combination of those two guys is one of the most dynamic... combinations on the planet," Palm said. Yeah, right. The real process was a creeping reorganization in which Rubinstein replaced the old Palm executive team in stages. I think Palm would have been better off with a single quick transition in which the new team was put in place all at once and given time to coalesce.

But if Palm moved too slowly on organizational change, it probably moved too quickly on product shipment. The Pre shipped without a finished development environment, frustrating the developers who were most motivated to create interesting software on it. And it had an OS that hadn't been tuned properly for performance, so even its most enthusiastic users had to apologize for its lack of responsiveness. Although there was a lot of pressure on Palm at the time to ship, in retrospect the company would have been far, far better off if it had waited a few more months and shipped a product that delivered a great user and developer experience.


4. What you do, do well. The old Palm's "zen" design principles said: "Find a problem, find the simplest solution, punt the rest." It was an appliance design philosophy translated into computing. The new Palm tried to boil the ocean. Its ambition to create a smartphone platform superior to iPhone forced it to compete on a very broad range of fronts, everything from OS to SDK to app store to hardware. Inevitably, Palm wasn't able to execute equally well in all areas, and some of the Pre's features were compromised due to lack of resources. Apple can get away with a flawed version one product because it has the financial resources to go back and fix its mistakes. Which brings me to the fifth lesson...


5. You're not Apple. Trying to beat Apple head-on is a rich man's game, the computing equivalent of fighting a land war in Asia. There are effective ways to compete with Apple on a budget, but they all involve avoiding or neutralizing its strengths, and targeting segments or tactics that Apple can't or won't pursue. Instead, Palm attacked head on. I'm picturing that Warner Brothers cartoon where Black Knight Yosemite Sam charges at full speed into the wall of a castle and bounces off flat as a pancake (link).


What it means for the rest of us

You'll notice that I didn't say anything about Palm's bizarre ads featuring a Borg hive queen (here and here). That's because they were a symptom, not a cause. When your product is right, the message will be simple and you won't need creepy ads to stand out. Often you won't need ads at all.

The mistakes highlighted by Palm are common in the tech industry. Here's what I think we should do about them:

--I know there are device companies out there right now where the employees are whispering to each other, "we've committed to shipping on a certain date, but the product won't really be ready." You know who you are. Don't let your company pull a Pre; speak up. If nothing else works, print this post and send it to your boss. The Board of Directors might fire you if you delay the launch, but they definitely will fire you if the product fails.

--I frequently talk with companies that are creating bundles of technologies rather than coherent solutions to problems (anybody want to buy a Verizon Droid? link). Ask yourself, who is my customer, and am I solving a problem that they care about deeply?

--I know investors who say, "I'll never touch hardware, it's too risky." Understand that you're missing opportunities where you could invest with a higher return, because valuations aren't being bid up by competing investors. The fault, dear investor, is not in our product category, but in our execution.


That's my take. What do you think? Where did Palm go wrong (if at all), and what do you think the lessons are for other companies?

Symbian: Evolving toward open

It's fascinating to watch the evolution as Symbian remakes itself from a traditional OS company into an open-source foundation. They've made enormous organizational changes (most of the management team is new), but the biggest change of all seems to be in mindset. A nonprofit foundation has a very different set of motivations and priorities than an OS corporation does. I get the feeling that the Symbian folks are still figuring out what that means. It's an interesting case study, but also a good example for companies looking to work with open source.

Symbian recently held a dinner with developers and bloggers in Silicon Valley, and I got to see some of those differences in action.

The first difference was the dinner itself. About six months ago, Symbian and Nokia held a conference and blogger dinner in San Francisco (link). It was interesting but pretty standard -- a day of presentations, followed by dinner at a large, long table at which Symbian and Nokia employees talked to us about what they're doing and how excited they are. The emphasis was on them informing us.

The recent dinner was structured very differently. The attendees were mostly developers rather than bloggers, and we were seated at smaller, circular tables that made conversation easier. They talked about their plans at the start, but most of the evening was devoted to asking our opinions, and they had a note-taker at each table. This had the effect of not just collecting feedback from us, but forcing us to notice that they were listening. That's important to any company, but it is critical to a nonprofit foundation that relies on others to do its OS programming. And it's essential for a company like Symbian, which has been ignored by most Silicon Valley developers.

So that's the first lesson about open source. The task of marketing is no longer to convince people how smart you are, it's to convince people how wonderful you are to work with. Instead of you as a performer and developers as the audience, the situation is flipped -- the developers are the center of attention and you're their most ardent fan.

It's an interesting contrast to Apple's relationship with developers, isn't it? It'll be fun to see how this evolves over time.

Here are my notes on the subjects Symbian discussed with us, along with some comments from me:


It takes time

Symbian said its goal is to have a lot of developers on the platform and making money, but that can't be achieved in three months. "In three years time," is what I wrote in my notes. That is simultaneously very honest and a little scary. It's honest because a foundation with its limited resources, working through phone companies with 24 month release cycles, simply can't make anything happen quickly. It's scary because competitors like Apple and RIM have so much momentum, and can act quickly. Still, in the current overused catchphrase of sports broadcasting, is what it is. An open-source company, based on trust, simply cannot afford to risk that trust by hyping or overpromising.

Speaking of Apple and RIM, Symbian made clear that it considers its adversary to be single-company ecosystems like Apple, RIM, and Microsoft. I didn't think to ask if Nokia's Ovi fits in that category, but that probably wouldn't have been a polite question anyway. Symbian also took some swipes at Google, citing the "lock in" deals they have supposedly made with some operators.

You get the feeling that Symbian is intensely annoyed by Google. It's one thing for a mobile phone newcomer like Apple to create a successful device; it's quite another for an Internet company to step into the OS business and take away Motorola as a Symbian licensee. I think one of Symbian's arguments against Android is going to be that Symbian is more properly and thoroughly open.

The question is whether anyone cares about that. Although the details of open source governance are intensely important to the community of free software advocates, I think that for most developers and handset companies the only "open" that they care about translates as, "open to me making a lot of money without someone else getting in the way." Thus the success of the Apple Store, even though Apple is one of the most proprietary companies in computing. Symbian's measure of success with developers will be whether it can help them get rich -- and I think the company knows that.


Licensees and devices

One step in helping developers make money is to get more devices with Symbian OS on them. Symbian said phones are coming from Chinese network equipment conglomerates Huawei and ZTE. They also said non- phone devices are in the works.

Licensees will be especially important if Nokia, as rumored, creates a line of phones based on its Maemo Linux platform. Lately some industry people I trust have talked about those phones as a sure thing rather than speculation, and analyst Richard Windsor is predicting big challenges for Symbian as a result:

"It seems that the clock is ticking for Symbian as technological limitations could lead to it being replaced in some high-end devices.... I suspect that the reality is that Symbian is not good enough for some of the functionality Nokia has planned over the medium term leaving Nokia with no choice but to move on."
Source: Richard Windsor, Industry Specialist, Nomura Securities

David Wood at Symbian responded that people should view Maemo as just Nokia's insurance in case something goes wrong with Symbian (link). But the point remains that Nokia is Symbian's main backer today. That is a strength, but also a big vulnerability. If Symbian wants developers to invest in it, I think it needs to demonstrate the ability to attract a more diverse set of strong supporters.


App Store envy

Another way to help developers is to, well, help them directly. Symbian said it's planning something tentatively called "Symbian Arena," in which it will select 100 Symbian applications to be featured in the application stores on Symbian phones. Symbian will promote the applications and perform other functions equivalent to a book publisher, including possibly giving the app author an advance on royalties.

The first five applications will be chosen by July, and featured on at least three Symbian smartphones (the Nokia N97, and phones from Samsung and Sony Ericsson).

The most interesting aspect of the program is that Symbian said its goal is to take no cut at all from app revenue for its services. Obviously that means the program can't scale to thousands of applications -- Symbian can't afford it. They said they'd like to evolve it into a much broader program in which they would provide publishing services for thousands of apps at cost. My guess is they could push the revenue cut down to well under 10% in that case, compared to the 30% Apple takes today.

It isn't clear to me if Symbian will produce the applications store itself, or work through others, or both. If it works through other stores, those stores might take a revenue cut of their own. But still, from a developer point of view it's nice to see an OS vendor trying to lower the cost of business for creating apps.

It's been interesting to see how many of the Palm Pre reviews this week have said that the iPhone application base is the main reason to prefer an iPhone over a Pre. I'm not sure how much purchase influence apps actually have -- at Palm, we had ten times the applications of Pocket PC, but they didn't seem to do anything for our sales. (On the other hand, Palm never had the wisdom and courage to advertise its apps base the way Apple has.)

--"Compared to the iPhone, the real missing pieces are those thousands of applications available on the App Store." Wired
--"Developer courting still seems like an area where Palm needs work. They've got a great OS to work with, but they have yet to really extend a hand to a wide selection of developers or help explain how working in webOS will be beneficial to their business. The platform is nothing without the support of creative and active partners." Engadget
--"The Pre's biggest disadvantage is its app store, the App Catalog. At launch, it has only about a dozen apps, compared with over 40,000 for the iPhone, and thousands each for the G1 and the modern BlackBerry models....It is thoughtfully designed, works well and could give the iPhone and BlackBerry strong competition -- but only if it fixes its app store and can attract third-party developers." Walt Mossberg

Anyway, if applications are the new competitive frontier between smart phones, mobile OS vendors should be competing to see who can do the most to improve life for developers. This is another area where Symbian's motives, as a foundation, differ from a traditional OS company. If you're trying to make money from an OS, harvesting some revenue from developers make sense. But as a nonprofit foundation, draining the revenue streams from your competitors is one of your best competitive weapons. Symbian has little reason to try to make a profit from developers, and a lot of reasons not to.


Driving Web standards

That idea came up again when we talked about web applications for mobile. As I've said before, I think the most valuable thing that could happen for mobile developers would be the creation of a universal runtime layer for mobile web apps -- software that would let them write an app once, host it online, and run it unmodified on any mobile OS. No commercial OS companies want to support that because it would commoditize their businesses and drain their revenues. But if Symbian's primary weapon is to remove revenue from other OS companies, a universal Web runtime might be the best way to do it. I asked them about this, and they said they're planning to use web standards in the OS "like Pre," and said they're interested in supporting universal web runtimes.

I'm intensely interested in seeing how the runtime situation develops. I think Symbian and Google are the only major mobile players with an interest in making it work, and Google so far hasn't been an effective leader in that space. I think Symbian might be able to pull it off, and become a major player in the rise of the metaplatform. But it'll take an active effort by them, such as choosing a runtime, building it into every copy Symbian OS, and making it available for other platforms. Passive endorsement of something is not enough to make a difference.


Other tidbits

Symbian said it's going to "radically simplify" the Symbian Signed app certification program, which may be very welcome news to developers, depending on the details. Many developers today complain bitterly about the cost and inconvenience of the signing program, and unless it's fixed it'll outweigh any of the benefits from Symbian Arena.

The QT software layer that Nokia bought as part of its Trolltech acquisition will be built into Symbian OS in the second half of 2010. I had been wondering if it would be an option or a standard part of the OS; apparently it'll be a standard.

Symbian plans to bring its developer conference to San Francisco in 2010, after which it will rotate to various locations around the world. This is part of an effort to increase Symbian's visibility in the US market. The company is creating a large office here, including two members of its exec staff. That makes sense for recruiting web developers, but it will be hard for the company to have a big impact in the US unless it gets a licensee who can market effectively here. In that vein, it must have been frustrating for everyone involved when Nokia announced the shipment of the N97 and it came in a distant third in coverage in the US (after the Palm Pre and the iPhone rumors).


What it all means

There are a lot of things that could kill the Symbian experiment:
--Nokia could decommit from the OS (or just waver long enough that developers lose faith).
--Symbian licensees could fail to produce interesting devices that keep pace with Apples, RIMs, and Palms of the world.
--Android could eat up all the attention of open source developers, leaving Symbian to wither technologically.
--The market might evolve faster than a foundation yoked to handset companies can adjust.

But still the Symbian foundation is worth watching. It has a different set of goals than every other mobile OS company out there, goals that potentially can align more closely with the interests of third party developers. It's still up to Symbian to deliver on that potential, but the company has an opportunity to challenge the mobile market in ways that it couldn't as a traditional company.

-----

Prof. Joel West of San Jose State was also at the Symbian meeting and posted some interesting comments about it. You can read them here.

Full disclosure: My employer, Rubicon Consulting, did a consulting project for Symbian a year ago. None of the analysis conducted in that project was used in this post. We currently have no ongoing, or planned, business relationship with Symbian.

The Palm Pre: Think Similar

Palm died. Palm OS died. Get over it.

Now let's talk about this new company, and product, that happens to be named Palm. I don't know if they'll survive or not, but they have a chance, and they're definitely interesting.

That was my overall impression after visiting Palm at CES 2009. The differences started with the meeting room itself. Rather than shelling out for a (very expensive) booth, Palm had an upstairs display room off the show floor. That in itself is not unusual; companies low on money often take a display room at CES so they can have some sort of presence at the show. Usually they get very little traffic, because you have to make an effort to find them.

But there was a short line outside Palm's room. A friend and I got into line, and the Palm folks asked us for our business cards. They went away for about 30 seconds, came back, and pulled us both out of line. "You can go right in."

I'm not sure why they did it, since neither of us are VIPs. But somebody was screening the cards and pulling out anyone whose name they recognized. That was the first sign that I was dealing with a different company -- although the old Palm was pretty well organized, that level of attention to detail would have been unusual.

The second difference came when we entered the room itself. A display room at CES usually is an empty space about 40 feet (13m) or more on a side, with one big presentation screen, some chairs, and a couple of demo stations along the walls. You can take in the whole thing in 30 seconds. Instead, Palm had divided its space into almost a maze, with little meeting rooms (lined with couches) and corridors, all set off by gauze curtains. Along the "corridors" were abundant food carts (with servers, another unusual touch), and small stations where employees were giving continuous Pre demos to groups of up to about a dozen people. You could get very close and intimate with the device, although no touching was allowed.

It felt like a technology harem.

I don't think the old Palm would have decorated quite like that, let alone shell out that much money for exhibit space in a time of layoffs and financial stress.

The presenters were extremely well briefed and disciplined, although they didn't feel robotic. They showed the features they wanted us to see, and wouldn't be baited into going further. The overall impression of the space and staff was extreme design consciousness, a bit of opulence, and intense discipline.

Very un-Palm-like. More like boutique Apple without the rock star CEO.


Think Similar

The theme continued in the product. The Pre does not look like the Treo or any previous Palm product. If anything, it looks like an iPhone with some of its limitations fixed. The design of the hardware, graphics, the fonts, the way things move on screen, and the touchscreen gestures are all elegant, and reminded me intensely of the iPhone. You can even do a pinch gesture to shrink and expand things, which I thought was patented by Apple (this shows why I'm not a lawyer).

Unlike an iPhone, you can run multiple applications at the same time and switch between them. There's a thumb keyboard built in. The battery can be replaced. The APIs are supposedly based on web standards, so many people should be able to program the Pre without learning a new OS. Palm says it will have a software store built in, but the app approval process won't be as restrictive as Apple's. Palm will also apparently allow companies to port other platforms, like Adobe Flash, to the Pre, which addresses another iPhone drawback. (There's a comparison table between the iPhone and Pre here, but it focuses mostly on hardware specs.)

In contrast to all the iPhone references, it's very hard to spot any Palm legacy in the Pre (other than the company logo). The calendar still compresses unused hours, which was one of my favorite Palm features. But literally that was the main similarity that I noticed.

The device won't run current Palm OS apps, although I think Palm is open to someone porting a Palm OS emulator to the device if they want to. But I don't know how you'd operate those apps without a stylus. The browser is based on Webkit, so no more Blazer (yay).

The design of the interface looks nothing like Palm OS. Palm's old design ethic was all about sacrificing beauty in order to produce maximum utility. The result was often extremely efficient but plain (okay, ugly). The new Palm treats aesthetics like Apple does -- the device has to be useful, playful, and beautiful. That's incredibly hard to design, but apparently Palm has imported enough Apple talent to pull it off (or at least to make the demos look good).


Will Palm survive?

Prior to CES, it was fashionable for a lot of people online to predict Palm's imminent demise. That was a misreading of how the world works -- we technology insiders lose interest in a brand long before the public does. Palm still has a strong name, and it will get a good hearing in the market.

So the real question is, is the Pre good enough to make Palm profitable? I think it's too early to answer.

For one thing, we can't touch the product yet. The canned demos were incomplete -- I didn't see the dialer or the software store, for example, and I don't know details of how the product will sync. The SDK hasn't been released, so we don't know what it will be like to create apps for the device.

But my biggest concern is about the strategy, not the product. I'm not sure who the customer is for the Pre. Dr. Rob Enderle took time off from diagnosing Steve Jobs' medical condition (link) to tell a San Jose radio station that the Pre is a better e-mail device than the iPhone and a better consumer device than a Blackberry. Which is probably true, but misses the point -- it's probably a worse entertainment device than the iPhone (because it doesn't have iTunes) and probably a worse e-mail device than RIM (because it doesn't have RIM's server infrastructure). So who exactly is it best for?

Mobile devices that sell well usually have a well-defined market of people who look at them and say, "that one's perfect for me." The Pre is intensely elegant, which intrigues aficionados like me, but there aren't enough of us to make a lasting market. Beyond that, it's apparently perfect for people who want a compromise between a Blackberry and an iPhone, but don't need the best of either. Who are those people? And are there enough of them to make a business for Palm? I honestly don't know.

I guess the old Palm installed base might be a first source of customers, but many of them have moved on. Although there's a lot of enthusiasm on the Palm discussion forums (for a wonderfully detailed article, check here), longtime Palm users don't appear to have a lot of compelling ties holding them to the new device. Their old apps won't work, and they'll have to learn a new interface. Usually when a company makes a transition like this without backward compatibility, the user base reads it as an invitation to consider alternatives. Palm cannot take them for granted -- and even if it could, they alone are not enough to sustain the company.


What it means for the industry

Regardless of whether Palm survives, I think the Pre does some important things to the industry. It's the first smartphone that matches the iPhone on overall UI aesthetics, and it fixes many of the drawbacks of the iPhone. Other smartphone companies will be under pressure to match the Pre's features. Mobile companies like Samsung and Motorola, which lack software expertise, look increasingly vulnerable to gradual share erosion.

I'm very hopeful about the application development model for the Pre. By basing its development model on web standards, Palm apparently will empower the world's vast base of web app developers to quickly create Pre applications. If Palm implements the APIs right, that is a very smart move. It aligns Palm with the forces of the web, and might even make Pre the preferred mobile development platform of the web app community.

I don't know if that alone can make the Pre a success -- mobile devices usually build a base first with a particular function and then branch into apps. But it gives Palm a much better shot than it would have had if it tried to create yet another proprietary platform. The brass ring in the mobile app world is getting the attention of the web app community, and Palm now has a shot at it.

Google, are you listening?


What to do if you're a user

Wait.

We'll learn tons more about the Pre as it gets closer to shipping. Apple's undoubtedly working on new iPhone products (I'm betting on a smaller device, like a Nano version of the iPhone), RIM's getting the Storm debugged, Nokia is finishing the N97, and there are rumored to be more Android devices coming.* If you're thinking about getting a smartphone, you're going to have a great selection later this year. Hold out until you understand more about your choices.

__________

*There are probably some more Windows Mobile products coming too, but does anyone care any more?