Spellingmistakes inthe name ofthe appProvide adetailedinterface tocustomizeyour profileInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasInherit userinterfacecontrols as partof a screenshotfrom anotherappChoice ofcolour schemeis based onpersonalpreferencesUser experienceevaluation doesnot mention thespecific interfacedesignReflectionsconsist ofexcusesEnsureuserscreateaccountsWalkthroughpresentationdoesn't actuallymention theuser interfaceEnsure yourapp hasfeatures fromevery other appyou've everusedAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes onthe userinterfaceDivide thedesign amongstteam membersand each worksindependentlyTask analysisgenerates astructure whichis just the menulayoutA team memberindicates(implicitly) thatnobody elsecontributedBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen Documentationis independentof the appdesignQuestionsslide at theend of thewalkthroughpresentationThe quality of theinterface isproportional to thenumber of featuresprovided by theappForce loginbut neveruse accountinformationThe interfacematches anexisting appwith controls indifferentpositionsSpend morethan half thewalkthroughdiscussinglogging inReflectionsfocus on thetool used tocreate thewalkthroughSpellingmistakes inthe name ofthe appProvide adetailedinterface tocustomizeyour profileInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasInherit userinterfacecontrols as partof a screenshotfrom anotherappChoice ofcolour schemeis based onpersonalpreferencesUser experienceevaluation doesnot mention thespecific interfacedesignReflectionsconsist ofexcusesEnsureuserscreateaccountsWalkthroughpresentationdoesn't actuallymention theuser interfaceEnsure yourapp hasfeatures fromevery other appyou've everusedAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes onthe userinterfaceDivide thedesign amongstteam membersand each worksindependentlyTask analysisgenerates astructure whichis just the menulayoutA team memberindicates(implicitly) thatnobody elsecontributedBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen Documentationis independentof the appdesignQuestionsslide at theend of thewalkthroughpresentationThe quality of theinterface isproportional to thenumber of featuresprovided by theappForce loginbut neveruse accountinformationThe interfacematches anexisting appwith controls indifferentpositionsSpend morethan half thewalkthroughdiscussinglogging inReflectionsfocus on thetool used tocreate thewalkthrough

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