Second round of feedback from the DIA on the 'flatland' idea

[James William Yoon]

Forgot to cc the list.

On Fri, Feb 26, 2010 at 1:51 PM, James William Yoon
<james.yoon at utoronto.ca>wrote:

> Hey Alistair, Lee, Alison,
>
> We got another great round of feedback from the DIA (David, Jennifer, Matt)
> on the latest kiosk wireframes yesterday. Overall, they seemed to really
> like it, as in the meeting previous to this. Here's the lowdown of some of
> the thoughts that came out:
>
> - There was a thought about the possibility of showing not just the path
> visitor took, but also the future path too (maybe in the form of a outlined
> 'future' screen?)
>
> - There was a bit of debate about the position and layout of the screen
> bubbles--at least one thought that the animation would suffice to keep users
> oriented and cognizant that previous screens are being moved off to the
> side, but another felt that the positioning of bubbles in the lower right
> isn't entirely intuitive; easy fix for this one: just move it over to the
> left
>
> - 360 panoramic views could be potentially expensive to produce for every
> gallery
>
> - The gallery view wireframe currently has just the right amount of text
>
> - We need to make the relationships between screens and the content
> structure more salient
>
> - Vertical vs. horizontal orientation:
>   - Vertical orientation might make it work better for maps (which are
> vertically oriented at the DIA), and for putting path of screens in the
> lower sections
>   - Ergonomic factors: vertical orientation makes reach and head position
> potentially more difficult
>
> - We don't need a "print tour" function--instead, frame it as, here's the
> map, and "print the map" instead.
>   - Will users be inclined to look at the map?
>   - Should we put in a "mini map" by default?
>
> - On print brochure design: what kinds of images do we use to identify the
> gallery?
>   - Customize it on a case-by-case basis: use iconic artifacts for some,
> and image of the space for others
>
> - They really like the ability to bounce back and forth between screens
>   - Interesting that this came up, because I intentionally never explicitly
> explained the affordance of bouncing "forth" from a "back"--it's something
> they intuitively expected from the rest of the design
>   - We didn't discuss in detail what happens to the current screen when you
> bounce to a previous screen--does it stay there? Does it disappear?
>
> - How do we distinguish between the buttons for theme vs. that of gallery?
>   - Matt likes the icon for a theme idea (would we animate it?)
>   - Let's brainstorm possible icons for themes using the current theme list
> draft
>
> Have a read over these comments, and let's meet soonish to talk over what
> changes to put in.
>
> Cheers,
> James
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100226/1c2cb50a/attachment.html>