Developing for webOS: the experience

October 23rd, 2009 § 0

Mojo code

When I first started developing for Palm I was a bit skeptical of the framework because it seemed thrown together and needed a lot of polish. The most annoying part was (and is) the lack of accurate documentation. Yes, I said accurate. Palm’s Developer website doesn’t offer complete documentation on everything, and even less of it is actually accurate. Often times if you copy-and-paste the sample code into your project it will not work due to either a typo in their code or the fact that the code is from a previous version of the framework and no longer works.

Palm’s own developer forums often are a frustration. If you take a look around you’ll notice a trend: most people’s posts have many more views than replies—which tells me nobody else can help them either. This isn’t to discount the webOS/Mojo ninjas out there—it just grows both aggravating and disappointing. I am currently trudging through writing a follow-up app for my last one, with progress alternating between very quick and very aggravatingly slow (as in, spending an entire day trying to figure out a problem no one has the answer to, and eventually deciding on another path that actually works).

Although this post sounds like a rant, I wouldn’t classify it as one. I haven’t lost faith in Palm. I understand it’s very early in webOS’s lifespan (indeed, the App Catalog itself is still in Beta), and being a developer I can accept that 1.x software is seldom perfect. Although being in the Palm camp this early on is a bit frustrating, seeing the ratings and feedback from your users after your app has finally shipped makes it all worth it.

Where Am I?

You are currently browsing entries tagged with development at zacharytamas.