T WITCH G AME D EVELOPER L IBRARY F INAL P RESENTATION UX Design - - PowerPoint PPT Presentation

t witch g ame d eveloper l ibrary f inal p resentation
SMART_READER_LITE
LIVE PREVIEW

T WITCH G AME D EVELOPER L IBRARY F INAL P RESENTATION UX Design - - PowerPoint PPT Presentation

T WITCH G AME D EVELOPER L IBRARY F INAL P RESENTATION UX Design Alexis Miller 8/11/15 Amazon | Twitch Seattle | Confidential P RESENTATION O VERVIEW I. UX Design Spec II. Design Customer Scenario III. Developer Customer Scenario IV.


slide-1
SLIDE 1

Amazon | Twitch Seattle | Confidential

TWITCH GAME DEVELOPER LIBRARY FINAL PRESENTATION

UX Design — Alexis Miller 8/11/15

slide-2
SLIDE 2

2

  • I. UX Design Spec
  • II. Design Customer Scenario
  • III. Developer Customer Scenario
  • IV. Producer Customer Scenario
  • V. Conclusion

PRESENTATION OVERVIEW

slide-3
SLIDE 3

UX DESIGN SPEC

3

slide-4
SLIDE 4

4

  • I. Documentation with code samples
  • II. Search (internal & external)
  • III. “Task-driven” information architecture
  • IV. Game-maker role filter system
  • V. Browsing & search
  • VI. Clear call to action

VII.Timeline of product & feature releases VIII.Visually group information on the Article Page

DESIGN REQUIREMENTS

slide-5
SLIDE 5

FOCUSED DESIGN

5

slide-6
SLIDE 6

6

slide-7
SLIDE 7

7

Call to Action Prominent Search Links to Article Links to Article Landing Page All Categories listed, links to Article Landing Page Browsing Back to Twitch.tv

slide-8
SLIDE 8

8

Visually group content Task-driven information architecture Game-maker role filter system

Article Landing Page

slide-9
SLIDE 9

9

Content pulled by tagging system Articles + Forum links Code samples Page feedback Table of contents for page

Article Page

Easy to copy & paste

slide-10
SLIDE 10

SCALABLE DESIGN

10

slide-11
SLIDE 11

11

slide-12
SLIDE 12

12

slide-13
SLIDE 13

13

Timeline of Product & Features Toggle between posts by moving date cursor or clicking on image below timeline Content pulled from blog.twitch.tv/category/dev Links to blog Call to Action Twitch Identity for video feed

slide-14
SLIDE 14

14

Browsing

slide-15
SLIDE 15

15

Three additional video feeds Live feed of from Game Development Feed Twitch hosts live office hours

slide-16
SLIDE 16

16

Links to Blog Back to Twitch.tv

slide-17
SLIDE 17

17

Visually group content Task-driven information architecture Game-maker role filter system

Article Landing Page

slide-18
SLIDE 18

18

Content pulled by tagging system Articles + Forum links Code samples Page feedback Table of contents for page

Article Page

Easy to copy & paste

slide-19
SLIDE 19

CUSTOMER SCENARIO: GAME DESIGNER LOOKS FOR IDEAS

19

slide-20
SLIDE 20

20

Kim arrives on the home page from a Google Search. She scans the content & clicks

  • n Getting Started

Getting Started takes Kim to an article page Kim scans the page and looks at

  • ther articles in

the category She finds a cool idea and shares the page link with her colleagues Kim wants to

  • ptimize her game

for Twitch but doesn’t know where to start

slide-21
SLIDE 21

21

slide-22
SLIDE 22

22

slide-23
SLIDE 23

23

slide-24
SLIDE 24

24

slide-25
SLIDE 25

25

slide-26
SLIDE 26

26

slide-27
SLIDE 27

CUSTOMER SCENARIO: GAME DEVELOPER SEARCH FOR A QUICK ANSWER

27

slide-28
SLIDE 28

28

Carlos needs to find the Twitch REST API reference list He types some key words into a Google Search The first hit takes him to a landing page in Twitch documentation Carlos uses a quick link on the page to navigate to the API information After the page loads Carlos searches for a keyword using control F Carlos doesn’t see the object he

  • needs. A

discussion link catches his eye & he clicks on it

slide-29
SLIDE 29

29

slide-30
SLIDE 30

30

slide-31
SLIDE 31

31

slide-32
SLIDE 32

32

discuss.dev.twitch.tv

slide-33
SLIDE 33

CUSTOMER SCENARIO: GAME PRODUCER FINDS PRODUCT ROADMAP

33

slide-34
SLIDE 34

34

Mark is planning his development roadmap and needs to know when Twitch will release new features Mark arrives on the home page from a Google Search The timeline immediately catches his eye Mark plays around with the timeline, reading the recent updates & older updates Mark looks at the prospective timeline dates & finds relevant information

slide-35
SLIDE 35

35

slide-36
SLIDE 36

36

slide-37
SLIDE 37

37

Goes to Blog Returns

slide-38
SLIDE 38

38

Goes to Blog

slide-39
SLIDE 39

CONCLUSION

39

slide-40
SLIDE 40

40

WHAT I LEARNED

Communicate with stakeholders who have different perspectives & motivations Communicate high level direction while nose-deep in the project Design work is never done

slide-41
SLIDE 41

41

Graduate May 2016 B.A. Interactive Entertainment & Game Design, Minor Entrepreneurship

WHAT’S NEXT

President, Delta Omicron Zeta Professional Leadership Fraternity

slide-42
SLIDE 42

42

Yuyi Hsu, Abizar Vakharia, Sella Rush, Stephen Wang, David McLeod, Aaron Krasnov, Allen Lee, and Trenton Payne

THANK YOU!

slide-43
SLIDE 43

ALEXIS MILLER

43

anmiller@usc.edu lexinteractive.co https://www.linkedin.com/pub/alexis-miller/3a/914/532

slide-44
SLIDE 44

QUESTIONS

44

slide-45
SLIDE 45

45

APPENDIX

Direction | Summary | Methodology | Detailed Findings | Assumptions | Next Steps

Descrip(on Opera(on Time ¡(sec) Move ¡pointer ¡to ¡Doc ¡ Dropdown P ¡[menu ¡item] 1.10 Click ¡on ¡Doc ¡ Dropdown K ¡[mouse] 0.2 Consider ¡what ¡to ¡do ¡ next M ¡[key ¡word] 2.15 Move ¡pointer ¡to ¡Topic P ¡[nav] 1.10 Click ¡on ¡Topic K ¡[mouse] 0.2 Move ¡pointer ¡to ¡ content ¡area P ¡[content] 1.10 Scroll ¡Page H ¡[content] 0.4 Control ¡F K ¡[content] 0.2 Eyes ¡adjust ¡to ¡info ¡ jump H ¡[content] 0.4 6.85 Descrip(on Opera(on Time ¡(sec) Move ¡pointer ¡to ¡Doc ¡ Dropdown P ¡[menu ¡item] 1.10 Click ¡on ¡Doc ¡ Dropdown K ¡[mouse] 0.2 Consider ¡what ¡to ¡do ¡ next M ¡[key ¡word] 2.15 Move ¡pointer ¡to ¡Topic P ¡[nav] 1.10 Click ¡on ¡Topic K ¡[mouse] 0.2 Move ¡pointer ¡to ¡ content ¡area P ¡[content] 1.10 Scroll ¡Page H ¡[content] 0.4 Control ¡F K ¡[content] 0.2 Eyes ¡adjust ¡to ¡info ¡ jump H ¡[content] 0.4 Didn’t ¡find ¡correct ¡info H ¡[content] 0.4 Move ¡pointer ¡to ¡nav P ¡[nav] 1.10 Click ¡on ¡Sub ¡Topic K ¡[mouse] 0.2 Move ¡pointer ¡to ¡ content ¡area P ¡[content] 1.10 Control ¡F K ¡[content] 0.2 Eyes ¡adjust ¡to ¡info ¡ jump H ¡[content] 0.4 9.65

GOMS/ KLM Methodology K = pressing a key or button P = pointing with the mouse to a target on display H = moving hands to the home position on the keyboard or mouse M = mentally preparing for a task Appropriate Page Lengths Page length needs to support the primary use of the web page. Longer pages are acceptable to:

  • Facilitate uninterrupted reading, especially on content pages
  • Simplify page maintenance
  • Make pages more convenient to download and print
  • Support control F

SubTopics on Different Pages Singular Topic Page

Time it takes to arrive on Topic Page & begin to find answer

Reasoning behind singular topic pages