Comments on: Mobile Ajax: Safari Browser

By: MOBILE Model (on-road vehicles)- OTAQ - EPA - Mobile Links

MOBILE Model (on-road vehicles)- OTAQ - EPA - Mobile Links — Tue, 20 Jun 2006 13:52:55 +0000

[...] Ajaxian MobileWatch the IE Mobile Team blog for further details on our DOM support. Mobile Ajax Example. Microsoft put up a working demo for an example of accessing the current K-Index for a given location so that people [...]

By: think

think — Fri, 19 May 2006 15:13:07 +0000

why wait?

there are more than 30 million ajax enabled phones in the market already (see overview at http://opera.com/products/mobile/products/)

By: Jim

Jim — Fri, 19 May 2006 05:18:30 +0000

It’s probably true that many (but not all) of the design constraints for mobile also hold for accessibility on the desktop. For example, the lack of a mouse is true for both. If Ajax is to grow up, keyboard and voice navigation will have to be part of the story; this will help both mobile users and disabled ones.

By: Me

Me — Wed, 17 May 2006 08:43:01 +0000

Well, for starters, it would help, if the Nokia browser would run on older Series60 phones too, not only on latest and greatest.

Developers will not bother with testing for minority browsers they don’t have access to. Right now, Nokia’s attitude to older feature packs is not helping.

By: gaffney.wsj2.com

gaffney.wsj2.com — Wed, 17 May 2006 00:49:03 +0000

Mobile Ajax, Ruby on Rails and the RIM Blackberry

I was reading some great stuff about the Mobile Web over at Ajaxian. Designing for small screens presents some unique challenges and in his latest post, Dion Almaer does a great job of highlighting some of the key ones. I’ve been spending a great dea

By: CellphoneSavant

CellphoneSavant — Tue, 16 May 2006 19:55:51 +0000

Thanks for the post. I am new to your blog and I like what i see. I look forward to your future work.

By: Mom

Mom — Tue, 16 May 2006 17:13:06 +0000

algorythmically = algorithmically

By: leMel

leMel — Tue, 16 May 2006 16:22:04 +0000

My answer? Sites should be designed with mobile access in mind from the start.

What do developers need in order to do this? Stable, well-defined, standardized mobile platform (as few as possible) with clear, published development cycles.

Judging fron the fact that we’ve only just begun to approach this on desktop browsers doesn’t leave me optimistic. But I believe that’s the answer, if anyone cares.