HP Reportedly Sought $1.2 Billion for Palm and webOS - HotHardware
HP Reportedly Sought $1.2 Billion for Palm and webOS

HP Reportedly Sought $1.2 Billion for Palm and webOS

Hewlett-Packard spent the majority of 2011 chasing its tail and getting nowhere in the process. Maybe 2012 will be better, and in some respects, it almost has to be. On the fail scale, it's hard to top shopping your PC division when it's the biggest in the world, buying a British software firm for $12 billion as part of a shift in strategy by a soon-to-be-ousted CEO, and open-sourcing webOS after spending $1.2 billion acquiring Palm a year prior.

It gets better (worse?). According to new information obtained by VentureBeat, the reason HP couldn't find a suitor for Palm is because its asking price was simply too high. Inexplicably, HP was asking $1.2 billion for Palm, the exact same price it paid one year ago before bungling the acquisition, and then somehow expecting not to take a loss after the whole TouchPad fiasco. Was HP really oblivious to Palm's lost value?


Credit: ABC Corp.

"At one point, HP’s team tried to pitch the sale to Facebook but was practically laughed out of the room," VentureBeat reports.

HP might have lowered its price after failing to find a suitor willing to bail them out for $1.2 billion, but realistically, Palm would probably have be offered at half the price HP paid for it, if not less. Chalk it up to just another silly decision by HP during a year the company would like to forget.
0
+ -

$1.2 billion for Palm? And what would you get for that? A Linux operating system kernel with a touch based GUI on top of that?

Don't get me wrong... WebOS looks pretty sweet. But it's not that sweet. A great system architect (they exist) combined with a great UI designer (also exist), a good standard for project management (they don't exist... but we manage) can design and implement a full Linux based smart phone platform for $10-$15 million in a year. Marketing drones should get a bunch of money to hype the hell of it during that time too. Make it exciting and mysterious.

Step 1) Decide on a language

Step 2) Decide on a GUI toolkit... no don't make one yourself you moron

Step 3) Decide on the applications you need to make it happen

Step 4) DO NOT ALLOW system level headers to be used. Everything must be abstracted

Step 5) Develop an emulator

Step 6) Develop a shell (this is the "desktop" or home screen or whatever)

Step 7) Get a team to develop each application and issue feature requests for new APIs they need.

Step 8) Polish the APIs, document the *** out of them.

Step 9) Use an iPhone or Android phone or whatever else you have on hand to get users testing it

Step 10) Change the device to make it better based on user feedback.

Step 11) Ship it

Step 12) Work on the next release

A calculator program takes a day to write. It takes a month to make great.

An on screen keyboard... easy enough unless you decide to reinvent the wheel... again.

A notes program... easy

A web browser... if you used a decent tool kit... make the UI... easy.

A clock.. easy

etc...

Power management will be an issue... not that big of one though. This was handled by Apple the best possible way... stop the applications which are not visible from running at all... then setup an event interface that allows the background apps to respond to external stimuli (like an incoming message or a timer event). Then, don't allow any apps which behave differently into your store.

The hardest part of making a smartphone platform is actually the configuration mechanism. It's not as hard as it seems though. Just requires a bit of thought. Wireless networking and GSM communication are the hardest parts. For this... it can take a few months to make something good.

Now... here's the REALLY hard part... make the thing sync with Windows, Exchange and Mac. This is a non-option. The best way to do this is simple... setup a Internet based gateway. Write a sync client for each system... and of course don't bother with the exchange... just use the Linux based exchange connectors directly on the phone.

There's lots of other stuff too... but those are apps. Like video playing and downloading (the API already does most of this for you), audio playing and downloading, book reading, etc... But this is a problem for the application developers.

In short... there's no good reason to buy something like WebOS for a billion. As a matter of fact, forking Meego or just using Android is far more intelligent.

Login or Register to Comment
Post a Comment
Username:   Password: