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.
Brookefield Call Girls: đ 7737669865 đ High Profile Model Escorts | Bangalore...
Â
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.