3 ms·
I love my iPhone. But giving developers the option to cook up apps in HTML/JS is a very slick move. I don't know how it'll play out, but any average web develo
by bprater 18y ago
I love my iPhone. But giving developers the option to cook up apps in HTML/JS is a very slick move.
I don't know how it'll play out, but any average web developer will be able to immediately pump out an app without breaking open a iPhone SDK tome.
I don't know if it's possible to advance against the AppStore line of offense, but it's a seriously smart move.
I think their next coup should be to create an "open framework" so that other phone designers can latch on to whatever OS-specific hooks Palm plans on using.
I feel like this is critical. It can't be a closed framework.
- anatoli 18y agoWhile I don't disagree that there is something nifty about HTML/CSS/JS apps, I think we've all seen that this is not enough. Remember, first iPhone was in the same position - no SDK, just "widgets" and that didn't exactly fly with the developers. As somebody who's developed some widgets, I can say that there just isn't enough to go on in JavaScript to create full-powered apps, such as the ones available on iPhone now. More importantly, in regards to this: "any average web developer will be able to immediately pump out an app without breaking open a iPhone SDK tome." Any average web developer can pump out a widget for iPhone, afaik, so I would disagree that this is an advantage that the Palm Pre has.
- bprater 18y agoWidget, maybe. I was specifically talking about something akin to a "native" app. You need hooks to the OS, period, for developers to be happy. Maybe we need a new word for HTML/JS/CSS apps that have OS-specific hooks. Widget is a horrible word.