Hola Jorge, > Everybody is optimizing their website to iPhone UI, but what about the > others touch screen devices?
Some of our clients are actually getting the two confused. "touch screen" = "high end browser", at least in their minds. We re-educate them (Opera Mobile??), and frequently recommend a four-version approach (applies to web sites, not to apps): 1. touch/stylus + client scripting 2. scroll-and-select + client scripting 3. server-side scripting <-- includes transcoders like Novarra, OpenWeb, Google, etc. 4. nonscripting You use a little device detection to make minor tweaks to the last two. For example, increase target size or padding size if it is a touch device. You can combine 1 & 2 if you need to; you can combine 3 & 4 if you must. The distinction between server-side and client-side is critical, but not obvious to clients. Basically, server-side (like Opera Mini) will display the page, but won't re-draw parts of the page. It cripples responsiveness. Finally, we added a page to our wiki about what script *events* each browser can generate. Anybody with deep knowledge of S60 and Pocket IE is especially encouraged to participate. http://patterns.littlespringsdesign.com/index.php/Script_Events -- Barbara Ballard [EMAIL PROTECTED] 1-785-838-3003 Design For Mobile 22-24 September http://design4mobile.mobi/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
