Comments on: How the iPhone is Causing Web Design to Go Backwards http://www.afhill.com/blog/iphone-design-backwards/ Reflections on online strategy, social media marketing, web accessibility and interactive design. Tue, 07 Feb 2012 22:14:21 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Eric Filson http://www.afhill.com/blog/iphone-design-backwards/#comment-154311 Eric Filson Fri, 27 Feb 2009 18:08:56 +0000 http://www.afhill.com/blog/?p=1772#comment-154311 Soo... you could also just leave everything in place as it is... If you're serious about designing for the iPhone you should be displaying a site BUILT for the iPhone... If your back end is worth anything it's built using the MVC pattern and the only thing you have to do is swap your views for iPhone users. Just do a check against the user agent :P Soo… you could also just leave everything in place as it is… If you’re serious about designing for the iPhone you should be displaying a site BUILT for the iPhone…

If your back end is worth anything it’s built using the MVC pattern and the only thing you have to do is swap your views for iPhone users. Just do a check against the user agent :P

]]> By: Andrea Hill http://www.afhill.com/blog/iphone-design-backwards/#comment-144276 Andrea Hill Tue, 10 Feb 2009 14:30:59 +0000 http://www.afhill.com/blog/?p=1772#comment-144276 Exactly, while "going backwards" has a negative connotation, I think it's actually an exciting point. Time for us to rethink all the bells and whistles to determine what value they add (and unfortunately for me as a non-Creative, I don't always appreciate all the nuance!) Exactly, while “going backwards” has a negative connotation, I think it’s actually an exciting point. Time for us to rethink all the bells and whistles to determine what value they add (and unfortunately for me as a non-Creative, I don’t always appreciate all the nuance!)

]]> By: JGoh http://www.afhill.com/blog/iphone-design-backwards/#comment-144237 JGoh Mon, 09 Feb 2009 17:36:51 +0000 http://www.afhill.com/blog/?p=1772#comment-144237 Is this a case of removing everything except the elephant from web design? I think occasionally looking at an interface (or algorithm, or room, or anything really) and removing things is probably a good idea. I hadn't realized just how much I ignore when I go to websites in a full-fledged desktop browser; I really just want to get at my information and get out. " Perfection is achieved, not when there is nothing left to add, but when there is nothing left to remove. -- Antoine de Saint-Exupery " We've spent a lot of time adding. Time to remove before we start adding even more. :) Is this a case of removing everything except the elephant from web design?

I think occasionally looking at an interface (or algorithm, or room, or anything really) and removing things is probably a good idea. I hadn’t realized just how much I ignore when I go to websites in a full-fledged desktop browser; I really just want to get at my information and get out.

” Perfection is achieved, not when there is nothing left to add, but when there is nothing left to remove. — Antoine de Saint-Exupery ”

We’ve spent a lot of time adding. Time to remove before we start adding even more. :)

]]> By: Mobile Web Design And Superbowl Ads | StayGoLinks http://www.afhill.com/blog/iphone-design-backwards/#comment-142404 Mobile Web Design And Superbowl Ads | StayGoLinks Fri, 06 Feb 2009 21:16:23 +0000 http://www.afhill.com/blog/?p=1772#comment-142404 [...] it the KISS-lite principle.   Putting that in other words, as Andrea Hill points out, Web Design Must Go Backwards.  User expectations will result in changes in how we design for the [...] [...] it the KISS-lite principle.   Putting that in other words, as Andrea Hill points out, Web Design Must Go Backwards.  User expectations will result in changes in how we design for the [...]

]]> By: webstandardsmag (Webstandards-Magazin) http://www.afhill.com/blog/iphone-design-backwards/#comment-141155 webstandardsmag (Webstandards-Magazin) Thu, 05 Feb 2009 08:31:38 +0000 http://www.afhill.com/blog/?p=1772#comment-141155 <div style='float:left;margin-right:10px;padding:0;width:60px;height:60px;background:url(http://www.chatcatcher.com/images/picbg.jpg) no-repeat top;'></div><div style='float:left;margin-left:-70px;margin-right:10px;padding:0;width:60px;height:60px;'></div>Ahill sammelt, wie sich mit dem iPhone das Webdesign verändern wird [link to post] - ein Rückschritt?<br /><br /> - Posted using Chat Catcher

Ahill sammelt, wie sich mit dem iPhone das Webdesign verändern wird [link to post] – ein Rückschritt?

– Posted using Chat Catcher

]]> By: Andrea Hill http://www.afhill.com/blog/iphone-design-backwards/#comment-141142 Andrea Hill Wed, 04 Feb 2009 23:31:23 +0000 http://www.afhill.com/blog/?p=1772#comment-141142 Hmmm, very interesting idea! I can't imagine how difficult it would be, but it would be great to have a general idea of the different "gotchas" Hmmm, very interesting idea! I can’t imagine how difficult it would be, but it would be great to have a general idea of the different “gotchas”

]]> By: k|torz http://www.afhill.com/blog/iphone-design-backwards/#comment-141141 k|torz Wed, 04 Feb 2009 23:28:37 +0000 http://www.afhill.com/blog/?p=1772#comment-141141 And I always thought that a mobile phone was just to phone .... And I always thought that a mobile phone was just to phone ….

]]> By: D. Lambert http://www.afhill.com/blog/iphone-design-backwards/#comment-141104 D. Lambert Wed, 04 Feb 2009 22:26:16 +0000 http://www.afhill.com/blog/?p=1772#comment-141104 Good point. Wouldn't it be nice to have a "code coverage"-type tool that could show you the parts of your app that any given UI rendering device can't access? Good point. Wouldn’t it be nice to have a “code coverage”-type tool that could show you the parts of your app that any given UI rendering device can’t access?

]]> By: Andrea Hill http://www.afhill.com/blog/iphone-design-backwards/#comment-141100 Andrea Hill Wed, 04 Feb 2009 22:21:40 +0000 http://www.afhill.com/blog/?p=1772#comment-141100 I don't see it as a "problem" unique to mobile - users of assistive technologies like screen readers have never been able to "hover" over elements. Mobile just helps make people more aware of these design considerations. I'm actually happy that people need to be more conscious of strong design and not haphazardly hiding important information. I don’t see it as a “problem” unique to mobile – users of assistive technologies like screen readers have never been able to “hover” over elements. Mobile just helps make people more aware of these design considerations. I’m actually happy that people need to be more conscious of strong design and not haphazardly hiding important information.

]]> By: D. Lambert http://www.afhill.com/blog/iphone-design-backwards/#comment-141098 D. Lambert Wed, 04 Feb 2009 22:17:57 +0000 http://www.afhill.com/blog/?p=1772#comment-141098 I ran into the hover problem on my Win Mobile phone a while back: <a href="http://blog.componentoriented.com/?p=150">On Tooltips and Affordances</a> I ran into the hover problem on my Win Mobile phone a while back:

On Tooltips and Affordances

]]>