Why I’m not building for the Palm Pre
(or lots of these other “webOS” platforms)
So the other day while at Mobile Monday Miami (disclosure, I’m on the executive committee) someone asked if I was going to start porting my apps to Palm’s new Pre platform. I responded with a resounding NO, maybe too hastily, but I still stand by my response.
So you might be thinking, well its cheaper to build for the Pre, and theoretically building for the Pre is the same as building for the web right? Well the Pre is only the first handset in Palm’s WebOS plan, so we don’t know if the future handsets will have the same specs, or dimensions, or capabilities, so making apps becomes more fractured. iPhone development is simple, all the phones or iPods have the same screen resolution, same capabilities, and are uniform worldwide. As a web developer who has been building web apps for a decade, hassling with all the different browsers and operating system nuances has been a royal pain, and the last thing I want to do is deal with 5 different phone configurations which serve maybe a few thousand users.
Now if Palm sends me a few unlocked PREs with free data/phone cards in them, I’ll happily dive more into it and let you all know what i think, but realistically that same offer would apply to Google with their Android (which I could talk about later and have many similar gripes).
In the end it all boils down to a cost per user acquisition, and costs to support each user. In a bootstrap economy, we’ve all got to take those things into consideration.
UpdateI was pointed to this link that @whurley(who is a kick-ass community leader in texas) posted about his experiences with palm. Worth the read. via @mherzber. Also worth reading is @giovanni‘s reaction to Pre.