Provide adetailedinterface tocustomizeyour profileDocumentationis independentof the appdesignSpellingmistakes inthe name ofthe appInterfaceevaluationrequires thatthe user findbugs in theapplicationInherit userinterfacecontrols as partof a screenshotfrom anotherappThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceBuild yourinterface usingscreenshotsfrom an existingappReflectionsconsist ofexcusesAn interfacedesign onlyrequires choiceof colours, fontsand iconsA teammember isonly asource ofideasThe interfacematches anexisting appwith controls indifferentpositionsDivide thedesign amongstteam membersand each worksindependentlySpend morethan half thewalkthroughdiscussinglogging inChoice ofcolour schemeis based onpersonalpreferencesQuestionsslide at theend of thewalkthroughpresentationA team memberindicates(implicitly) thatnobody elsecontributedTask analysisgenerates astructure whichis just the menulayoutStart witha loginscreen Force loginbut neveruse accountinformationUser experienceevaluation doesnot mention thespecific interfacedesignEnsureuserscreateaccountsEnsure yourapp hasfeatures fromevery other appyou've everusedProvide adetailedinterface tocustomizeyour profileDocumentationis independentof the appdesignSpellingmistakes inthe name ofthe appInterfaceevaluationrequires thatthe user findbugs in theapplicationInherit userinterfacecontrols as partof a screenshotfrom anotherappThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceBuild yourinterface usingscreenshotsfrom an existingappReflectionsconsist ofexcusesAn interfacedesign onlyrequires choiceof colours, fontsand iconsA teammember isonly asource ofideasThe interfacematches anexisting appwith controls indifferentpositionsDivide thedesign amongstteam membersand each worksindependentlySpend morethan half thewalkthroughdiscussinglogging inChoice ofcolour schemeis based onpersonalpreferencesQuestionsslide at theend of thewalkthroughpresentationA team memberindicates(implicitly) thatnobody elsecontributedTask analysisgenerates astructure whichis just the menulayoutStart witha loginscreen Force loginbut neveruse accountinformationUser experienceevaluation doesnot mention thespecific interfacedesignEnsureuserscreateaccountsEnsure yourapp hasfeatures fromevery other appyou've everused

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