Developers Still Anticipating a Positive WebOS Experience
Application Development Trends Magazine has posted a new article showcasing the continued strong feedback from developers about Palm's WebOS. Entitled "Will Palm Get its ‘Mojo' Back with WebOS and Pre?" the piece is written by ADT editor Jeffrey Schwartz.
In short, ADT surmises that the general consensus amongst the developer is that Palm is back from the brink of oblivion with a compelling, developer-friendly new mobile platform and device. The piece also discusses the various PreDevCamps, which are being formed and operated totally autonomously from Sprint, Palm Inc., or the Palm Developer Network.
ADT interestingly asserts that many Pre developers are attracted to the platform out of dissatisfaction with the difficulty in iPhone development versus the ease in developing for WebOS, not to mention the continued criticisms levied against Apple's licensing and iTunes publishing terms, as evidenced over the recent furor over the rejected Nine Inch Nails iTunes app.
Of course, the usual positive attributes for develops are still hailed by the article, such as the appeal of WebOS' multitasking and Synergy components for integrating all possible data sources. Also covered are the usual questions surrounding WebOS' lack of integrated legacy support for classic Palm OS apps as well as the limited carrier availability of the Pre.
Mitch Allen, Palm's Software Chief Technology Officer and author of the upcoming Palm WebOS development book by O'Reilly Media, is quoted in his assessment of Palm's rival platforms:
"Apple has some excellent tools but it's still largely an embedded platform environment and BlackBerry is Java-based, though I am not very familiar with development on those platforms…but I think they are very different than WebOS, which is built around tools and models for Web applications. That implies a certain kind of workflow for the developer in terms of being able to build their applications fairly rapidly, iterate very rapidly using the kind of browser-based debugging tools. I think that workflow is a lot more productive than any of the embedded workflows, to be honest"