Live data from Hacker News

Designing for iPad: Reality Check

informationarchitects.jp

1–10 of 28 posts

Re: Designing for iPad: Reality Check

#2
Glad I'm not the only one who thought many of the popular iPad applications were silly.

The Average Reading Time idea is intriguing, however, I don't expect it to be of much use. Reading time varies vastly depending on the material. Nobody reads a journal article at the same pace as a novel, for instance.

Re: Designing for iPad: Reality Check

#3
Great article, this quote stuck out for me:

  The same rule applies to visual metaphors: Just as any
  literary metaphor, a visual metaphor confuses if it doesn’t
  clarify; it breaks if you stretch it; and it becomes
  ridiculous if you combine it with a second or third
  metaphor.

  Avoid metaphor that do not clarify; if a metaphor darkens
  the meaning of what you are trying to express, don’t use it.

Re: Designing for iPad: Reality Check

#4
post #2

Glad I'm not the only one who thought many of the popular iPad applications were silly. The Average Reading Time idea is intriguing, however, I don't expect it to be of much use. Reading time varies vastly depending on the material. Nobody reads a journal article at the same pace as a novel, for instance.

Average Reading Time certainly seems like something you would have to try if you want to find out whether it’s useful.

They should also drop the pseudo accuracy. Telling me the time down to the second (or are those minutes – hm, another source of confusion) seems ridiculous.

Re: Designing for iPad: Reality Check

#5
We found that the iPad applications we designed, made it relatively easy to be translated back into websites. The iPad could prove to be a wonderful blue print to design web sites and applications. If it works on the iPad, with a few tweaks, it will work on a laptop.

In that case you might as well skip the iPad application and focus on the cross-platform web application. Many of the current iPad applications don't really need to be native apps.

Re: Designing for iPad: Reality Check

#8
post #7
post #6

I read the whole thing and learned nothing about design for iPad. Confused.

What did you expect?

Some kind of a practical advice I could use in my work. If I knew what it looked like I might not need it. Maybe "we tried this and users hated it, but then we tried that and they loved it and lessons here is that that sort of things works better in such and such circumstances".

First of all, for many/most users iPad is a part of a different workflow compared to iPhone, and if people are to use it differently we should design differently.

Each iPhone's screen should serve single purpose and unambiguously lead to the next action. That way you get an app that can be used on the go. My guess is that this is not true for iPad, as it's not likely to be used on the go, so there will be a bigger preference towards multi-purpose screens. I would like someone to talk about that.

Re: Designing for iPad: Reality Check

#9
post #3

Great article, this quote stuck out for me: The same rule applies to visual metaphors: Just as any literary metaphor, a visual metaphor confuses if it doesn’t clarify; it breaks if you stretch it; and it becomes ridiculous if you combine it with a second or third metaphor. Avoid metaphor that do not clarify; if a metaphor darkens the meaning of what you are trying to express, don’t use it.

Huh?

Re: Designing for iPad: Reality Check

#10
post #9
post #3

Great article, this quote stuck out for me: The same rule applies to visual metaphors: Just as any literary metaphor, a visual metaphor confuses if it doesn’t clarify; it breaks if you stretch it; and it becomes ridiculous if you combine it with a second or third metaphor. Avoid metaphor that do not clarify; if a metaphor darkens the meaning of what you are trying to express, don’t use it.

Huh?

What part of the quote are you having trouble understanding, sir?
Post reply on HN