Why Palm Still Covets Palm OS
munchola wrote in with news that Palm has just announced a one-time payment for perpetual, royalty-free use of Palm OS. In 2005 Palm spun off PalmSource to an outside company, Access Systems Americas, and since that time has been paying out royalties for its use. At the same time Palm announced products based on Windows Mobile. Palm's latest announcement reduces the uncertainty among Palm OS developers. From the article: "In an unsurprising but symbolically important move, handheld and smartphone maker Palm this month signed a perpetual license with Access Systems Americas, which gives Palm the right to use Access' Palm OS operating system in whole or in part in any Palm device forever more. It sounds like a no-brainer, but the context is interesting, in particular what it means for the army of Palm OS developers out there. Believe it or not there are at least 160,000 Palm OS developers — and they're just the ones that Palm knows about."
The one place where Palm screwed up was in Hotsynch. It worked great on your personal computer, but it was a pain in enterprise environments. There was a point where palms were multiplying in companies like rabbits, but Palm left the enterprise support to third parties like Pumatech. As a result, they hit the wall where Microsoft was able to walk through the door, leveraging its position in corporate messaging. Blackberries also moved in by connecting to corproate email.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
A C-based API with a quirky event handling model, obscene attempts to preserve backward compatibility and somewhat loyal developers? Hmmm... I've never heard of that before.
I once used an iPAQ (w/ a brick-sized battery pack/PCMCIA slot accessory on it) almost religiously several years back. At that time, the iPAQ was great for keeping appointments, a few games stashed onboard, and to top it off, I could shove a PC Card adapter and a CF card full of mp3's in it, or a PC Card-based 802.11b card. It was fun to mess with and was even halfway practical.
Nowadays I can do pretty much all of that (and more) with an iPod and a decent cell phone - or just a really decent cell phone, methinks (except mine doesn't do mp3's, so...) So where does a stand-alone PDA fit in these days? Crackberries, yeah, I can see that - but it appears (IMHO) to be nothing more than a glorified cell phone with a really big screen, and definitely not something you'd want to tinker with under-the-hood too awful much, like you could with a PDA.
I guess I'm just curious, now with the increased power of mobile phone devices glommed together w/ PDA functions, if Palm's core business model even has a future, or if someday they'll just be sucked up by, say, Nokia or Motorola...
Does anyone actually use straight-up PDA's anymore?
Quo usque tandem abutere, Nimbus, patientia nostra?
http://www.access-company.com/about/opensource/ind ex.html
"We believe that everyone, partners and competitors alike, would benefit from the specification or development of a standard basic Linux platform for mobile phones. With an open and available platform, companies would be able to focus on their main areas of differentiation, develop phones cheaper, and get phones into the markets much faster."
"Q. Does this mean ALP will be open sourced?
A. We expect that we'll be contributing some of our technologies to the open source community as a part of this change. The user-visible parts of ALP (user interface, PIM applications, etc) and the Palm OS middleware will be a separate software layer on top of Linux, and will not be open sourced."
Hang on. He is lying because you don't know how he came up with that figure? And you back this up by just guessing that it is wrong and calling it reality.
He is just a blogger, so it is possible that he just made it all up, but that would only make him equally uninformed as yourself.
Every application or shared library has to have a unique, registered CreatorID. It would be easy to track which developers were still active (writing new programs) based on who was still submitting new CreatorIDs. I do not know if that is how this number was divined, but it does show that it could be accurate.
Just because you have not heard of all 160,000 developers does not mean to say that they do not exist. A lot of the development work is for in-house applications. I occassionally write some programs just for myself. Nothing ever gets published, so you would have never heard of me. That doesn't mean that I don't exist (I think).
If I am incorrect, and it turns out that I do not exist, then feel free to ignore me.
PalmOS is definitely stone-age internally, but guess what: being a PITA for programmers has *NOTHING* to do with its unmatched usability for end users.
I don't care how good WinCE's CLR is - it's a usability nightmare on a phone-sized device (why should I care what apps are running? I have zero interest in quitting this program to free up enough memory to run that program. The PIM functions also blow. And a Start menu? Please die.)
And J2ME is a very decent programming model? Yeah, great for programmers. Shitty for users. Have you ever actually *USED* third-party java apps on a Blackberry? I had the displeasure of having to carry one for $WORK years ago. Here's four words that sum up J2ME: "loading... um... still loading."
PalmOS is a crusty nightmare under the hood but somehow it's still the only thing out there that delivers a seamless *USER* experience. No loading time for app launches, excellent mapping of functions to single button presses or taps, etc.
When I want a system that's great for coders and tweakers, I use Linux on my desktop. I don't want that experience on my phone - I want a device that JUST WORKS NOW and lets me run the apps I want to run (devices that are closed to open-source or freeware developers fail it.)
Maybe Symbian will get there someday but the impression that I have is that it's entirely too carrier-friendly, not sufficiently user-friendly.
-Isaac
I am not a lawyer, and this is not legal advice. For Entertainment Purposes Only.
When I think "PalmOS", I don't think "programming model", I think GUI. Just because another OS is easier to program for doesn't make it "better" in any sense of the word that is meaningful to me. Running any variant of Windows on a phone seems nuts. This is not a little computer, folks. It's a phone (and a contacts manager, calendar, music player, picture shower, whatever), and it cries out for an interface that is simple, intuitive, and quick. Has anyone ever thruthfully used any of those words in the same sentence with "Windows"?
And don't forget that if you get a WinCE phone, it's going to expect you to sync with Outlook. The horror, oh the horror...
Great men are almost always bad men--Lord Acton's Corollary
Not only do you not need to, you don't want to. One reason the Palm succeeded where the Newton failed is it's sense of focus: the Palm is designed to be an adjunct to a PC, not a replacement for it.
That's not exactly what happened — the story has its history wrong. Palm did not sell PalmOS to Access. Palm split itself into PalmSource (software) and PalmOne (hardware), with joint ownership of the Palm brand. Later, PalmOne bought back the right to call itself "Palm", and PalmSource got bought out by Access.
Am I picking nits? I don't think so. All the investors in the old Palm ended up with stakes in the two new companies. And a software-only company was better positioned to be bought out by a company like Access, a buyout that must have been very profitable for PalmSource stockholders. Meanwhile, PalmOne/Palm is free to develop hardware that is not based on an OS that is quickly losing ground to Windows.
Also, you're wrong when you say all hardware is a commodity. PC hardware (or more precisely, PC motherboards) are a commodity, because they're produced on a huge scale by lots of different manufacturers who fight each other to sell them cheaply to big PC companies. But PalmOS-based PDAs have a tiny market with very little competition. Palm does not face the problems of commodity manufacturers (fierce competition to sell virtually identical products), it faces the problems of a specialized manufacturer that has gotten a little too specialized. If Palm survives at all, it will be as yet another manufacturer of smartphones, where competition is based as much on features as on price.
In that it kills the deal. It is not useable. With PalmOS, you get a dirt simple UI (no nested menus. I can get to any feature I use on my Treo with two button presses without looking), you get zero arbitrary restrictions (unlike the arbitrary screen resolution limit, and various other limits that Windows Mobile has to make it "not PocketPC"), and you get full hackability (which allows you to bypass all ridiculous carrier restrictions, and implement features that carries charge per-use for even though the device is capable of doing it on its own).
I don't care how hard it is to program for (but I've done it, and quite honestly I think a lot of developers are a bunch of whiners), and I don't think it is the best possible system, but it is the best one on the market right now, and nobody has caught up even though the platform has stagnated for over 10 years.
You are absolutely correct about PalmOS being the more user-friendly, even after many iterations of WinCE/WinMob. Case in point: What do you do to add a new appointment on PalmOS (since the original PalmPilot)? Click on the screen where (when) you want it and start writing. What do you do on WinCE/WinMob? Click on the "new" button, and when the dialog box pops up, click on the text entry area to write the description, then click on the date/time selector a bunch of times to set it, then click on "ok" to close the dialog box. How many different versions of WinCE/WinMob and they still don't have built-in support for in-line editing?
"They've canceled the show but we're still here. What does that make us?" "Big Damn Junkies, Sir!" "Ain't we just"