I’ve tried to be clear about my feelings concerning Palm’s late SDK release for WebOS, the operating system that runs the Pre. In my mind it’s a terrible, bass ackwards plan that’s done nothing to help Pre sales figures.

There was a bright light today, though, when I saw that the Mojo SDK Beta build had be leaked via torrent. That light’s still at the end of a long tunnel, though, as Palm maintains strict control over the final release build, and certainly won’t publish any apps made with the beta. The good is that developers can finally get their hands on development tools and start polishing their apps for a clean release, whenever that may be.

Palm also mentioned this week that they are adding developers to their early adoption program, doubling their membership this week. They predict the number should double again next week, though without an original stat, this might not be as many developers as I would hope.

At any rate, movement is movement, and at the very least the homebrew community just got a new toolset to fiddle with.

Palm continues to baffle me. I wrote a post the other day questioning the judgment behind withholding the WebOS SDK from the general public, and to day I find this article from Medialets. It’s an explanation of the Palm strategy to date concerning their App Catalog and includes one hugely disturbing fact.

Pre users have downloaded more than 600,000 apps.

When I read that my thoughts looked something like this: “..” “….” “……??!?!?!??!?!?!” Seriously, what the hell. The phone launch was a relative success, we know that. It wasn’t huge. It wasn’t earth-shattering, but for both Palm and Sprint it was a success.

People want apps, we know that. There have been more than a billion downloads on the iPhone, the Android market continues to grow, and now this. With just 30 apps in the Catalog, users are piling apps on to their phones. Why doesn’t the market at large have the SDK yet?

Medialets cites some interesting theories. First, most of the available apps are in beta. So what, the apps need more testing? Several of these apps are running version 0.9, as in, the last major revision before 1.0. Will they really be so different? Can developers even vouch for their app’s stability under hundreds of thousands of scrutinizing fingers? No, they can’t. Apps are nearly never bug-free at launch, and the growing pains of a new platform are part of the geeky fun of owning a brand new device.

Medialets also suggests the App Catalog isn’t ready for the deluge of submissions that would come with a public SDK. I can understand this. It’s a lot to sort through, and it’s no secret that Palm has been struggling. The number of people required to handle a hundred submissions a day, making sure they (the apps) won’t brick anyone’s Pre, is enormous. Paying those employees will be a serious expense, which leads us to the last problem: money.

It always comes down to money, and the App Catalog has no way to make any. As of today, there’s no payment system in place to reap the rewards of a well-developed app. Palm isn’t the only one hoping for a revenue stream from the store. Developers need to be paid for their time, and their best efforts should be justly rewarded, affording more time for people to put together more great apps.

The problem remains that this wasn’t planned well enough before the Pre’s launch. I can understand and even empathize with Palm for their troubles, but they botched this thing. You can’t expect to launch a phone like the Pre without planning for a payment system for apps you know people will want well in advance. I don’t want to hear “we’re working on it,” or “it’s not ready yet.” Those are crap excuses, and the only reason for them is a complete lack of foresight.

I like the Palm Pre. I really do. I’m starting to wonder, though, if Palm does.

For all the excitement surrounding their best phone release in years, Palm seems to be doing their damnedest to let the Pre slip into obscurity. Perhaps the best feature of the new Pre is its operating system, named webOS because it comes built on web technologies that supposedly make developing on the platform a breeze. The platform also supports multi-tasking, a feature missing from the Pre’s ‘roid-induced cousin, the iPhone Unfortunately, Palm has yet to release the webOS SDK, which would give developers a chance to put some great apps in the hands of Palm fans and iPhone malcontents. In fact, the SDK isn’t coming until the end of summer.

“We’ve been working very hard on the SDK and are eager to open access on a wider scale, but the software and the developer services to support it just aren’t ready yet,” says Palm. I have to ask, then, did they pick the right time to launch the phone? It’s all well and good to try to gain ground before the new iPhone drops, but why launch when a solid app development platform could greatly improve the phone’s appeal? There are plenty of unsatisfied Apple/AT&T customers. Why not pick them up in the wake of the 3GS?

As of today, the Pre’s App Catalog sits at just 30 apps. At that level, they have no chance. Even if there were a couple hundred the Pre might have just enough appeal to lure in some the folks who spurned Apple’s advances. Show them multi-tasking with apps they love and you could start to build a base of very satisfied customers, and that’s exactly the way to gain market share.

For now, a lot of Pre users are content to homebrew their apps, porting games like Doom and piecing together tethering on the fly. But that magic can only last so long before serious developers get bored, or get so entrenched in the iPhone or Blackberry development that they all but forget about the Pre. That’s something Palm can’t afford. We’ll see how hungry developers are by the end of summer, assuming they stick around.