Smack! Smack! Smack!

Ouch! That smarts!

Verizon [VZ] has now gotten two of  Palm’s [PALM] flagship devices that Sprint [S] has been touting, although some may say unsuccessfully due to the odd way that software developers and consumers have been treated– or at least very mixed– there’s that new question as to how Verizon will position these smartphones.

The TV commercials for the devices are already rolling out… and this is certainly a new entryway for Verizon to cater to Palm enthusiasts who have given up on the Garnet/Palm OS.

Microsoft [MSFT] and Nokia are finalizing an agreement to augment Nokia (particularly Symbian/S60-based) phones and smart devices into becoming viable business-grade devices, or even components in functional corporate meshes.

Management Perspective

Despite the consumer penetration by Apple [AAPL] in the smart mobile device market, neither it nor Palm [PALM] with its new Pre device or even Microsoft itself, with its Windows Mobile platform, have made the significant inroads that RIM [RIMM] with its various BlackBerry platforms have made in the business community. And while adoption of Nokia/S60, iPhone/iPod touch, Windows Mobile, and Android smart mobiles in the SMB segment has been tremendous, none of them have been able to make that tremendous security investment and network ubiquity that larger corporate entities demand.

Research in Motion: Problems

Not to say that RIM has completely protected its devices from espionage or other nefarious hacking attempts. But given their early adoption into businesses, BlackBerry devices have had the benefit of early market entry and dominance to keep its competitors at bay. But for the past few years, with the encroachment of the iPhone and its powerful distribution channel known as the iTunes App Store, RIM has had an increasingly difficult time justifying its add-on costs to tech-savvy companies that have very specialized needs that should not be restricted to the RIM network services.

Even worse, the BlackBerry devices actively marketed for business use carry hefty price tags that are beyond the hardware and assembly costs and yet are not as subsidized or discounted by the wireless carriers. This has become so extreme that many long-time BlackBerry owners have eked out a living by sticking with their old models.

Palm: Problems

Despite the recent rollout of the Pre, and the expected launch of the Eos, Palm has been limited to Sprint [S] for its wireless service on the Pre, while the more ubiquitous Centro and Treo smart devices continue to appeal to both businesses and consumers because of the stable Garnet OS platform and the wide plethora of applications available. In fact, despite the development onslaught of iPod/iPhone apps being released, the total software base of Palm OS/Garnet OS applications far exceeds every other mobile phones’.

But since Palm has essentially abandoned Garnet OS in favor of its newer webOS platform, the death knell for the Treo and Centro devices– while delayed– has been pealing for quite some time.

Android Consortium: Problems

While conceptually a good idea, Google’s [GOOG] open source Android platform seems to be suffering from too much expectation and not enough implementation realization. Instead of a tremendous groundswell of product releases and massive application software offerings, the problems associated with multi-vendor “cooperation” have curtailed widespread Android OS product adoption. This may be another case of early market advantage by Apple, or it may be merely due to developer community splintering and over-division.

Windows and Symbian OS: Opportunities

Combining the technologies found in Windows (and other Microsoft technologies) and Symbian OS platforms definitely provides quite an opportunity. Focusing on Nokia devices, traditionally non-Windows Mobile based throughout its history, allows for better standardization for application development, and it brings a huge developer community from the standard Windows OS, the portable Windows Mobile and CE platforms, and even interest from the XNA-Xbox networking groups. Additionally, the Maemo and S60 communities can be brought to bear to help flesh out both the Windows Mobile Marketplace and the Ovi Store.

Even more intriguing is Sun’s [JAVA] and Oracle’s Java Store (known on the distributor side as Java Warehouse) availability, given the strong presence of Java ME on Nokia smart devices. While Java Store has not been formally launched yet, finalizing the available revenue models for software developers who want to leverage that channel would benefit all of these potential collaborators. Combining Java technology (and JavaFX Mobile, too, ‘natch) with the distributed computing opportunities by the usual Sun-Java partnerships, like with Amazon [AMZN] Web Services and Elastic Cloud, as well as plenty of other hosting services (like Joyent) would further intensify and magnify the reach and coverage for businesses and corporate users.

And, of course, there would be plenty of consumer bleed-through opportunities as a result… Could you imagine purchasing Xbox LIVE games from your smartphone and having the option of either playing them on the ‘phone or having them ready to play at home via the download queue?

Natali del Conte (you remember her, right?) has mentioned in today’s Loaded episode that Verizon [VZ] is preparing to receive Palm [PALM] Pre devices on their network, sometime in 2010.

Of course, this makes sense, since there is not much retooling required for Palm, since both Sprint and Verizon run their cellular networks on CDMA/EvDO type networks. Unfortunately for Sprint [S], this spells the end of the exclusivity deal for the Pre device. And, unless they can successfully leverage the somewhat-buzz around the Mi-Fi device, particularly regarding its unusually steep pricing model for the product and its service plans, they will lose a lot of momentum once again.

Sprint [S] has finally released a press announcement concerning the Palm [PALM] Pre launch: June 6, 2009 is the official release date. The earlier speculation about the launch date appears within the range, and it sounds like the pricing is in line with other current smartphones offered by other carriers.

A lot of people, myself included, are a bit torn about the Palm Pre. It lacks the venerable yet reliable Palm OS (Garnet), instead running on its new webOS platform. It also is not available to a lot of long-time Sprint contract holders as an add-on, instead requiring a new two-year contract (obviously with a new TOS).

Developer Perspective

To developers, webOS presents a thorny problem.

Previously, the discussion about mobile software development was focused on the existing players, and that includes Palm OS. Of course, in addition to merely developing the applications, finding the appropriate marketplace for sales and marketing is key to success. When we last visited this subject, it was noted that there was no official centralized marketplace for Palm devices.

Now that webOS enters the arena, there is further fragmentation of the developer support for Palm devices: first, it began with PalmOS (Garnet), then Windows Mobile, and now webOS. While Palm claims that using JavaScript with their proprietary Mojo framework will ease development, the fact that it signifies a considerable amount of retooling for dev shops and studios (already driving their projects with Java, Objective-C, NS Basic, and various C++ flavors, just to name a few) is problematic at best. Some smaller shops may have already ruled out webOS and the Pre as a result, waiting to see the larger developers’ experiences with webOS. Unfortunately, this means that the explosive innovation that has highlighted the dramatic success of Apple’s [AAPL] App Store may not occur for Palm and the Pre.

In the meantime, both Apple and RIM [RIMM] have already made further inroads in expanding their user bases through greater distribution channels and product repricing. Other vendors have already begun constructing their own mobile app stores, so Palm would have to provide work overtime to appear developer-friendly and provide open access to the developer SDK.

Business Perspective

To many consumers and businesses, Palm has taken a backseat to strong contenders in the smartphone market. For a few years, it has been RIM, followed by Apple, and now HTC/Google [GOOG]. For many people, however, the Centro has been quite an interesting slim form factor, and with its attractive low price point and availability across multiple carriers, it has been quite a success for Palm. The question becomes whether the Pre should really be positioned as a premier product in the same category as the iPhone, T1, Bold, and Storm.

As a business, features that appeal to you tends to revolve around the communications features and app-specific capabilities for work activities. But since those features already exist in current smartphones, there is little incentive to switch carriers and devices unless there are contract expiration opportunities. Also, there are convergence devices like the iPod touch and netbooks that obviate the need for smartphones under many user scenarios.

As a consumer, if you are willing to be an early adopter, this would definitely be something to try. But if you are already satisfied with your current smartphone and do not require third-party apps, there would not be much need to switch, either, except for curiosity’s sake.

N.B.

Other related Javamancy posts (in reverse chronological order):

• More Palm Pre Release Date Speculation
• Palm OS Development Still Predominates
• Caveat Venditor: Profiting from Online Mobile App Stores
• Palm Pre Pricing and Availability Still Fuzzy
• Palm Pre

A lot of people are rightfully questioning whether the Palm Pre truly would fit in their current workflow or lifestyles.

Not surprisingly, the answer is most likely: NO.

After all, the Pre is an initial cut at a new product line, and it has much more in common with the older Treo models than, say, the Palm Centro (yep, remember the three-parter here, here, and here?), that darling of mass marketing and sales that has kept both Sprint [S] and Palm [PALM] viable for so long.

So, what then, is the upgrade path for Palm Centro owners?

Enter the Eos: a GSM-capable smartphone with a smaller form factor, akin to the Centro (supposedly), and headed for the AT&T [T] subscriber base… which means that Sprint customers will be left out once again, unless the rumors are false and/or there will be some heated negotiations between now and the launch date– perhaps any time in the 2H 2009? If even half of the Engadget tid-tad-bits are somewhat correct or near the mark, the Eos may become the real game changer for Palm against its competitors; but it will also distance Palm from its closest partner, Sprint.

Some people have speculated that the Eos will be PalmOS based, due to some unusual wording seen on briefing notes leaked to the public, but based upon Palm’s need to overhaul their smartphones’ software and keep up to date, combined with the cold relations between Access and Palm over Garnet OS, it is unlikely that Palm will issue the Eos with PalmOS/Garnet. Instead, it will probably be based upon the webOS platform first seen with the Palm Pre.

Well, you’ve probably heard about the previous rumored release date for the Palm [PALM] Pre being May 17, 2009…

The latest release date rumor has shifted the date to sometime between June 5 – 7, 2009, during a series of Palm corporate meetings, according to a leaked internal memo, as reported by The Boy Genius Report (BGR). This dovetails into a previous rumor, also reported by BGR, that the retailer Best Buy [BBY] would acquire several thousand units to sell at a “trial launch” event on June 7, 2009.

There is also speculation that this delayed launch date may be timed to defuse the expected tour de force that is the iPhone OS platform portfolio due at this year’s WWDC by Apple [AAPL].

N.B.

Other related Javamancy posts (in reverse chronological order):

• WWDC 2009 Sold Out
• Palm OS Development Still Predominates
• Caveat Venditor: Profiting from Online Mobile App Stores
• CTIA Wireless 2009
• iPhone OS 3.0 Preview Announcements Today
• Palm Treo Pro
• Palm Pre Pricing and Availability Still Fuzzy
• Palm Pre
• Developer Interest in iPhone Still High

More reading:

• Post at BGR on the new Pre launch date(s)
• Post at BGR on Best Buy trial launch of Palm Pre devices

The Setup

Back on July 17, 2008, I had an inkling of an idea… why not make Javamancy more friendly to mobile devices that are able to access the site? The date is significant because I’d recently acquired the Palm [PALM] Centro, and as I was trying out the provided Web browser (Blazer, the NetFront variant used by Palm on its more recent smartphones, not the older separate Blazer codebase) and realized that Javamancy was not quite as snappy on loading and display as I’d prefer. At the time, we were experimenting with AdSense, which given its significant performance degradation and serious privacy concerns, was eventually removed… so it was difficult at the time to determine whether it was AdSense or the underlying blog software, or even our content, that was choking performance.

Couple that with the release of Apple’s [AAPL] iPhone 3G and iPod touch mobile devices, and the burning desire to rush out a mobile-access version of Javamancy was not terribly high. And, admittedly, there was the rush to prepare and head out to the annual medical conference, out in Hawai’i (which was certainly an adventure unto itself).

The Premise

It is a fairly straightforward concept: present an mobile device screen alternative to the traditional Web browser, but continue to present the appropriate content as the user navigates through the blog.

It sounded easy when first proposed during the requirements meeting, but it turned out to be something a bit trickier.

The biggest concern was the continuing proliferation of mobile devices that would hit Javamancy. Ultimately, we realized that we were getting all sort of devices that we had not originally anticipated, with all sorts of different user-driven browsers and automated agents hitting the site. Since the concern is now known to be quite warranted and valid, any sort of solution for Javamancy Mobile would have to allow for some level of flexibility, in terms of quickly and accurately flagging devices that should have access to the mobile-access display.

But we also need to allow people who have the luxury of flexibility to be able to use the traditional Javamancy UI if they prefer.

The Action

At first, last year, there was some investigation that had occurred to see if there were any suitable plugins that would provide the desired features. We had encountered quite a few, including Alex King‘s WordPress Mobile Edition. At the time, however, during testing, something always seemed to break between the plugins and themes we had injected in the test beds. So rather than struggle with multiple variables (which often ends up similar to herding cats) or spin up extra test servers in QA and hack away, it was decided to postpone further investigation until some newer developments would ease the selection process… or we’d get angry enough to begin Coding in Anger.

Alex had recently released several updates to the WordPress Mobile Edition plugin, along with an accompanying Carrington Mobile theme that drives the UI. For our purposes, this seems to make more sense, particularly with the separation of concerns between browser detection/access and the subsequent UI functionality. As a result, after testing, we’ve launched Javamancy Mobile, courtesy of Alex’s fantastic products.

Keep it going, Alex!

According to the February 25, 2009 announcement from Black Duck Software in their recent report on mobile projects in 2008, the Palm OS platform remains the king of the heap with more than four times (4X) the number of total projects than the second place platform, the iPhone OS.

While Apple’s [AAPL] iPhone OS development projects are clearly leading the new, emerging projects, the total available software projects is still dominated by the venerable Palm OS (not to be confused with Windows Mobile software that may run on Palm WinMobile smartphones). Also, keep in mind that the latest incarnation of Palm OS, Garnet, may not always be fully compatible with much older software that was originally developed for the original Palm Pilot devices.

N.B.

Other related Javamancy posts (in reverse chronological order):

• Caveat Venditor: Profiting from Online Mobile App Stores
• The Wireless War Redux: Apple vs. RIM vs. HTC-Google
• The Wireless War: Apple vs. Palm vs. RIM

Remember Palm’s [PALM] Treo Pro?

If not, you’re apparently in good company. The smartphone was initially rolled out to a very hum of fanfare, being essentially an unsubsidized GSM device.

Now, however, it comes available as an AllTel [VZ] subsidized phone, with plans to offer Sprint [S] service in the hopefully near future. Obviously, unlike the previous GSM phone, these new models provide support for CDMA2000 and EvDO Rev A, which makes supporting AllTel/Verizon and Sprint networks possible.

This seems to come in the shadow of the trickling of Palm Pre news yesterday. While it certainly appears that there is little to differentiate one WinMobile 6.1 phone from the rest, having a workhorse alternative to the whiz-bang new devices on the block helps the bottom line.

Yesterday, Palm [PALM] and Sprint [S] revealed more information about the Palm Pre and its service plans in a Webcast, although still no definite release date or the phone pricing (subsidized or unsub, either). However, the release window of “sometime in the first half of 2009″ is presumably still more-or-less intact. Also, the Pre is expected to be attached to Sprint’s Simply Everything plans.

N.B.

For more information, found externally:

• On Gizmodo…
• On MobileCrunch (including slides from the Webcast)…

Remember the previous Palm Pre mention here?

• Palm Pre

… And in case you missed the epic saga of my smartphone selection process that culminated with the Centro, in chronological order:

• Palm Centro: The Beginning, Part 1
• Palm Centro: The Beginning, Part 2
• Palm Centro: The Beginning, Part 3