Questionsslide at theend of thewalkthroughpresentationDivide thedesign amongstteam membersand each worksindependentlyA team memberindicates(implicitly) thatnobody elsecontributedSpellingmistakes onthe userinterfaceReflectionsconsist ofexcusesForce loginbut neveruse accountinformationEnsure yourapp hasfeatures fromevery other appyou've everusedEnsureuserscreateaccountsInterfaceevaluationrequires thatthe user findbugs in theapplicationWalkthroughpresentationdoesn't actuallymention theuser interfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappInherit userinterfacecontrols as partof a screenshotfrom anotherappSpend morethan half thewalkthroughdiscussinglogging inReflectionsfocus on thetool used tocreate thewalkthroughProvide adetailedinterface tocustomizeyour profileThe interfacematches anexisting appwith controls indifferentpositionsDocumentationis independentof the appdesignAn interfacedesign onlyrequires choiceof colours, fontsand iconsA teammember isonly asource ofideasTask analysisgenerates astructure whichis just the menulayoutBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen User experienceevaluation doesnot mention thespecific interfacedesignSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferencesQuestionsslide at theend of thewalkthroughpresentationDivide thedesign amongstteam membersand each worksindependentlyA team memberindicates(implicitly) thatnobody elsecontributedSpellingmistakes onthe userinterfaceReflectionsconsist ofexcusesForce loginbut neveruse accountinformationEnsure yourapp hasfeatures fromevery other appyou've everusedEnsureuserscreateaccountsInterfaceevaluationrequires thatthe user findbugs in theapplicationWalkthroughpresentationdoesn't actuallymention theuser interfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappInherit userinterfacecontrols as partof a screenshotfrom anotherappSpend morethan half thewalkthroughdiscussinglogging inReflectionsfocus on thetool used tocreate thewalkthroughProvide adetailedinterface tocustomizeyour profileThe interfacematches anexisting appwith controls indifferentpositionsDocumentationis independentof the appdesignAn interfacedesign onlyrequires choiceof colours, fontsand iconsA teammember isonly asource ofideasTask analysisgenerates astructure whichis just the menulayoutBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen User experienceevaluation doesnot mention thespecific interfacedesignSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferences

App Interfaces with User Centered Design - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  1. Questions slide at the end of the walkthrough presentation
  2. Divide the design amongst team members and each works independently
  3. A team member indicates (implicitly) that nobody else contributed
  4. Spelling mistakes on the user interface
  5. Reflections consist of excuses
  6. Force login but never use account information
  7. Ensure your app has features from every other app you've ever used
  8. Ensure users create accounts
  9. Interface evaluation requires that the user find bugs in the application
  10. Walkthrough presentation doesn't actually mention the user interface
  11. The quality of the interface is proportional to the number of features provided by the app
  12. Inherit user interface controls as part of a screenshot from another app
  13. Spend more than half the walkthrough discussing logging in
  14. Reflections focus on the tool used to create the walkthrough
  15. Provide a detailed interface to customize your profile
  16. The interface matches an existing app with controls in different positions
  17. Documentation is independent of the app design
  18. An interface design only requires choice of colours, fonts and icons
  19. A team member is only a source of ideas
  20. Task analysis generates a structure which is just the menu layout
  21. Build your interface using screenshots from an existing app
  22. Start with a login screen
  23. User experience evaluation does not mention the specific interface design
  24. Spelling mistakes in the name of the app
  25. Choice of colour scheme is based on personal preferences