Comments on: iPhones and mobile browsing experience, design http://blog.aydindesign.com/2007/11/22/iphones-and-mobile-browsing-experience-design/ still trying to figure out what exactly this blog is all about Tue, 06 Jan 2009 15:07:45 +0000 http://wordpress.org/?v=2.2.1 By: nicola http://blog.aydindesign.com/2007/11/22/iphones-and-mobile-browsing-experience-design/#comment-17 nicola Tue, 27 Nov 2007 19:36:42 +0000 http://blog.aydindesign.com/2007/11/22/iphones-and-mobile-browsing-experience-design/#comment-17 Thank you very much Barbara, this is really helpful !I will definitely check out more details at dev.mobi. Writing versions for classes sounds more manageable than having to write different versions for every device. Its nice to think that there is a manageable way forward. A voice site sounds a great idea though, I am very new to this and hadn't heard of VoiceXML but I'm very keen to look at voice apps because I'm looking at designing handsfree mlearning so anything voice-based is ideal. I will check that out too. Thank you very much Barbara, this is really helpful !I will definitely check out more details at dev.mobi. Writing versions for classes sounds more manageable than having to write different versions for every device. Its nice to think that there is a manageable way forward.

A voice site sounds a great idea though, I am very new to this and hadn’t heard of VoiceXML but I’m very keen to look at voice apps because I’m looking at designing handsfree mlearning so anything voice-based is ideal. I will check that out too.

]]> By: Barbara Ballard http://blog.aydindesign.com/2007/11/22/iphones-and-mobile-browsing-experience-design/#comment-16 Barbara Ballard Mon, 26 Nov 2007 20:05:35 +0000 http://blog.aydindesign.com/2007/11/22/iphones-and-mobile-browsing-experience-design/#comment-16 I am a proponent of "class-based design". This is the practice of identifying classes of devices that may be accessing your site, writing different versions of the web site for each class, and then using the hacks to tweak for specific rendering issues. In the most obvious implementation, a "voice" web site authored in VoiceXML would need to have a different information architecture than a visual web site. Similarly, pages for a small-screen web site are not the same set of pages as a large-screen web site. On the other hand, many sites will never have the resources to do multiple versions of their site. For them, the Safari and Opera and Novarra and Google re-rendering of pages will need to be sufficient. Some tweaks can be done based perhaps on screen size, particularly using handheld media CSS and other tricks. Check out http://dev.mobi I am a proponent of “class-based design”. This is the practice of identifying classes of devices that may be accessing your site, writing different versions of the web site for each class, and then using the hacks to tweak for specific rendering issues.

In the most obvious implementation, a “voice” web site authored in VoiceXML would need to have a different information architecture than a visual web site. Similarly, pages for a small-screen web site are not the same set of pages as a large-screen web site.

On the other hand, many sites will never have the resources to do multiple versions of their site. For them, the Safari and Opera and Novarra and Google re-rendering of pages will need to be sufficient. Some tweaks can be done based perhaps on screen size, particularly using handheld media CSS and other tricks. Check out http://dev.mobi

]]>