iPad Human Interface Guide is an in-depth exploration on iPad app UX and is now publicly available:
http://developer.apple.com/iphone/library/documentation/Gene...
Designing for iPad: Reality Check
11–20 of 28 posts
Re: Designing for iPad: Reality Check
#12Earlier quoted context omitted.
Huh?
What part of the quote are you having trouble understanding, sir?
I think that it would be clearer if there were some examples of nested metaphors or metaphors that 'darken' other metaphors. Maybe there is in the actual text, but the quote out of context seems a little abstract.
Re: Designing for iPad: Reality Check
#13Earlier quoted context omitted.
What part of the quote are you having trouble understanding, sir?
I think that it would be clearer if there were some examples of nested metaphors or metaphors that 'darken' other metaphors. Maybe there is in the actual text, but the quote out of context seems a little abstract.
Indeed, there are plenty of examples in the text. I didn't think it necessary to paste the entire article in the comment box.
We'll have to agree to disagree.
Re: Designing for iPad: Reality Check
#14Glad 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.
It knows how quickly you change/scroll through pages while you read, so it can make a reasonable assumption of the number of words you read per minute and create an estimation that way.
Re: Designing for iPad: Reality Check
#15Glad 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.
It knows how quickly you change/scroll through pages while you read, so it can make a reasonable assumption of the number of words you read per minute and create an estimation that way.
Yes and no. I've tried this sort of thing before, and obviously the machine can't know when you are actually reading a paragraph slowly or when you've just been distracted. It would have to be clever about weighting an overall average with a short term average. I'll be curious to see how they do it, definitely.
Re: Designing for iPad: Reality Check
#16Earlier quoted context omitted.
I think that it would be clearer if there were some examples of nested metaphors or metaphors that 'darken' other metaphors. Maybe there is in the actual text, but the quote out of context seems a little abstract.
Indeed, there are plenty of examples in the text. I didn't think it necessary to paste the entire article in the comment box. We'll have to agree to disagree.
He didn't say an example was necessary, he said it could have made the quote clearer.
Re: Designing for iPad: Reality Check
#17I'm not sure I fully agree with his argument against using materials and textures to humanize a software interface. I do know that it requires a designer who's execution is better than average, but I don't think it's as much of a distraction as they proclaim. I also think it largely applies to the type of software one is designing. For example, the stock Notes app is fine but for Cultured Code's Things, it would not fit since task management is a much deeper interaction.
Anyhow, this article wasn't really informative, seems to be mostly opinion driven and the message is scattered. I showed the iPad to my parents this weekend, they were enamored by it because it was easy to relate with compared to their clunky Windows-based "laptops" -- a UX that's cold and impersonal.
Re: Designing for iPad: Reality Check
#18I'm not sure I fully agree with his argument against using materials and textures to humanize a software interface. I do know that it requires a designer who's execution is better than average, but I don't think it's as much of a distraction as they proclaim. I also think it largely applies to the type of software one is designing. For example, the stock Notes app is fine but for Cultured Code's Things, it would not…
Did you read the full article? Doesn't seem like it, since "it requires a designer who's execution is better than average" is exactly what it says. And not just that, it also defines the criteria for using metaphors and textures.
Re: Designing for iPad: Reality Check
#19Earlier quoted context omitted.
It knows how quickly you change/scroll through pages while you read, so it can make a reasonable assumption of the number of words you read per minute and create an estimation that way.
Yes and no. I've tried this sort of thing before, and obviously the machine can't know when you are actually reading a paragraph slowly or when you've just been distracted. It would have to be clever about weighting an overall average with a short term average. I'll be curious to see how they do it, definitely.
It says: "To find your average reading time all you need is taking a two minute test reading into one of the texts in the app and you’re set."
Re: Designing for iPad: Reality Check
#20Earlier quoted context omitted.
It knows how quickly you change/scroll through pages while you read, so it can make a reasonable assumption of the number of words you read per minute and create an estimation that way.
Yes and no. I've tried this sort of thing before, and obviously the machine can't know when you are actually reading a paragraph slowly or when you've just been distracted. It would have to be clever about weighting an overall average with a short term average. I'll be curious to see how they do it, definitely.
Good points. Given enough data it could do a decent job at normalizing lows & highs, enough to be useful anyway.
It would be interesting to see a proximity sensor in the iPad. I'm not sure what the range of those is. The accelerometer might be sensitive enough to detect when it's being held up as it's going to move a little bit in your hand.