In the session I talk about UX stumbling blocks and lessons learned when I developed a software for rear-projection screens and LED perimeter advertising systems for the local Basketball club. Even though I was developer, UX designer and user all in person, there were situations where I had problems using it under the time pressure of a home game, fueled by the fear of messing up in front of an audience of 6000 people.
CALL ON โฅ8923113531 ๐Call Girls Aminabad Lucknow best Night Fun service
ย
Fun, Confusion, Fear and Basketball (UX Lx 2014)
1. Fun, Confusion, Fear
โ and Basketball
Roland Weigelt
Comma Soft AG, Bonn, Germany
Roland.Weigelt@comma-soft.com
@rweigelt
mail@roland-weigelt.de
@RolandWeigelt (DE)
2. Roland Weigelt
โขComma Soft AG in Bonn, Germany
โข1997 โ Software Developer
๏ง Product INFONEAยฎ (Business Intelligence)
๏ง Frontend Development, interest in UIs in general
โข2012 โ UX Specialist / Senior Product Designer
๏ง Concepts, Mockups, etc. โ very little coding
๏ง Still writing software as a hobby
3. Hobby Turned Side Job
โขTelekom Baskets Bonn
๏ง BEKO BBL (1st German Division)
โขJob: Taking care of multimedia in the arena
๏ง Content creation, software development
Photo credit: Jรถrn Wolter, www.wolterfoto.de
4. โฆapplications Iโve written for the
๏ง rear projection screens
๏ง LED advertising system
โฆ(some) of the UI issues Iโve run into
โฆand the general lessons learned
Photo credit: Sebastian Derix, www.sebastianderix.de
This Talk is About...
10. Photo credit: Roland Weigelt
Captions
for the Live Camera
(aka โLower Thirdsโ)
11. Photo credit: Roland Weigelt
Captions
for the Live Camera
(aka โLower Thirdsโ)
12. Photo credit: Roland Weigelt
Captions
for the Live Camera
(aka โLower Thirdsโ)
โLiveTexterโ ๏ง Most captions are prepared
before the arena opens
๏ง Some have to be typed
โon the flyโ, within seconds
40. Preview
โขRear projection screens
๏ง 1024 x 768 Pixels
๏ง Scale down ๏ฎ OK!
๏ง Helps a lot
โข11 LED modules
๏ง 11 x 768 = 8448 Pixels
๏ง 80 Pixels high
๏ง No good โat a glanceโ
solution for all modules
43. Be Absolutely Clear
โขIf clicking โsomethingโ triggers a critical action,
๏ง make this โsomethingโ trivial to understand
๏ง under heavy stress
๏ง without even thinking.
45. Scrolling Messages
โขThe players of the home team
โขThe players of the guest team
โขThe members of the dance team
โขThe next home games
46. Home vs. Guest
โขThe official name of a match: โHome vs. Guestโ,
e.g. Telekom Baskets Bonn vs. ALBA BERLIN
โขNBA naming:
ALBA BERLIN at Telekom Baskets Bonn
47. Team Presentation
โข8 minutes before tip-off:
๏ง Lights out, loud music
๏ง โWelcome to todayโs match!โ
๏ง โTodayโs referees are...โ
๏ง โHere are the players of ALBA BERLINโ
๏ง โHereโs the Baskets Dance Team!โ
๏ง โAnd now, here are your Telekom Baskets Bonn!โ
58. Letโs Look Again
โขWhat do I want from a smooth transition?
๏ง From content A to content B
๏ง Within a certain timespan
๏ง Too short ๏ฎ not that different from a hard cut
๏ง Too long ๏ฎ timing not matching announcerโs voice
โขDo I really need to control the speed?
๏ง Experiments: 0.7 sec OK in most cases
60. Takeaways
โขHelp users build up confidence
๏ง Donโt be too subtle about state.
๏ง If possible, provide a preview.
๏ง Avoid internal translations: โDonโt make me thinkโ.
โขDecide if fine-grained control is necessary
๏ง Donโt sacrifice the usability of basic actions
๏ง But donโt take it away if users really need control.