The interfacematches anexisting appwith controls indifferentpositionsQuestionsslide at theend of thewalkthroughpresentationThe quality of theinterface isproportional to thenumber of featuresprovided by theappA teammember isonly asource ofideasInterfaceevaluationrequires thatthe user findbugs in theapplicationChoice ofcolour schemeis based onpersonalpreferencesReflectionsconsist ofexcusesReflectionsfocus on thetool used tocreate thewalkthroughA team memberindicates(implicitly) thatnobody elsecontributedInherit userinterfacecontrols as partof a screenshotfrom anotherappStart witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsForce loginbut neveruse accountinformationSpellingmistakes inthe name ofthe appUser experienceevaluation doesnot mention thespecific interfacedesignDivide thedesign amongstteam membersand each worksindependentlyBuild yourinterface usingscreenshotsfrom an existingappWalkthroughpresentationdoesn't actuallymention theuser interfaceEnsure yourapp hasfeatures fromevery other appyou've everusedTask analysisgenerates astructure whichis just the menulayoutProvide adetailedinterface tocustomizeyour profileSpend morethan half thewalkthroughdiscussinglogging inDocumentationis independentof the appdesignSpellingmistakes onthe userinterfaceEnsureuserscreateaccountsThe interfacematches anexisting appwith controls indifferentpositionsQuestionsslide at theend of thewalkthroughpresentationThe quality of theinterface isproportional to thenumber of featuresprovided by theappA teammember isonly asource ofideasInterfaceevaluationrequires thatthe user findbugs in theapplicationChoice ofcolour schemeis based onpersonalpreferencesReflectionsconsist ofexcusesReflectionsfocus on thetool used tocreate thewalkthroughA team memberindicates(implicitly) thatnobody elsecontributedInherit userinterfacecontrols as partof a screenshotfrom anotherappStart witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsForce loginbut neveruse accountinformationSpellingmistakes inthe name ofthe appUser experienceevaluation doesnot mention thespecific interfacedesignDivide thedesign amongstteam membersand each worksindependentlyBuild yourinterface usingscreenshotsfrom an existingappWalkthroughpresentationdoesn't actuallymention theuser interfaceEnsure yourapp hasfeatures fromevery other appyou've everusedTask analysisgenerates astructure whichis just the menulayoutProvide adetailedinterface tocustomizeyour profileSpend morethan half thewalkthroughdiscussinglogging inDocumentationis independentof the appdesignSpellingmistakes onthe userinterfaceEnsureuserscreateaccounts

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