I expected a touch-screen, too.
Part of that I'm speculatively thinking, was the fields of color for
each region.
The letters defining each region that map to the buttons, also got
lost with the map.
Maybe give the letterforms a flat-background to help them pop from the
background, without looking clickable but giving them more emphasis?
Go Arduino, go!
:) nina
On May 6, 2009, at 4:53 AM, Jordan, Courtney wrote:
Great job! I did expect a touch screen, where I could click the actual
stop name or colored region, rather than a physical button, and
similarly, that I could click the stop names once I had chosen a
region,
such as 19th St Oakland. This mental model expectation was created by
being able to interact with the dialog box via touch and of course,
interacting with newer ATMs. Since I don't live in an urban area that
provides that type of infrastructure, I wasn't used to the buttons and
letters corresponding to the soft keys (I dislike soft keys anyway,
especially in my cell phone). I did wonder why there are corresponding
letters when the letters don't provide any value or help to make
things
more understandable. If I clicked yellow, it shouldn't matter that
that
color corresponds to E. However, this might be a limitation of the
current physical design of the kiosk which might not have been within
the scope of your project. I liked how you made use of the limitations
of the physical buttons to enable the display of MORE choices. If the
buttons/letters aren't physical limitations, then it seems that
clicking
the actual stop name, rather than the button that is placed rather far
from it.
One idea (this is all fresh in my mind since I'm currently researching
ATM redesign for my company): Fifth Third (53.com) bank's ATM makes
the
soft keys look like large buttons with a little arrow pointing towards
the physical button, which seemed to integrate the software and
hardware
more, making it seem like the software interface design was deliberate
rather than showing that it was constrained to the limitations of the
physical design. But it does look like the blue arrows pointing into
the
screen rather than away at the buttons are part of the kiosk's
physical
constraints, so this kind of modification may not even be possible.
Courtney
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Ljuba Miljkovic
Sent: Tuesday, May 05, 2009 8:08 PM
To: [email protected]
Subject: [IxDA Discuss] Feedback on Redesigned BART Ticket Kiosk
Interface
I just finished my final UI design project at UC Berkeley's School of
Information (I'm a grad student there) and was hoping for your
feedback.
We redesigned the BART ticket kiosk.
Our goal was to make it easier for first-time or infrequent riders to
use while not making it any harder for experienced riders. The
software was built in Adobe Flex; the physical prototype was built
around a laptop and controlled by an Arduino micro-controller.
www.bartkiosk.com
Please check it out and let me know what you think.
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
