Force loginbut neveruse accountinformationThe interfacematches anexisting appwith controls indifferentpositionsChoice ofcolour schemeis based onpersonalpreferencesSpellingmistakes inthe name ofthe appThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughTask analysisgenerates astructure whichis just the menulayoutEnsure yourapp hasfeatures fromevery other appyou've everusedInherit userinterfacecontrols as partof a screenshotfrom anotherappA teammember isonly asource ofideasBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen Walkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyQuestionsslide at theend of thewalkthroughpresentationInterfaceevaluationrequires thatthe user findbugs in theapplicationProvide adetailedinterface tocustomizeyour profileSpend morethan half thewalkthroughdiscussinglogging inDocumentationis independentof the appdesignA team memberindicates(implicitly) thatnobody elsecontributedUser experienceevaluation doesnot mention thespecific interfacedesignSpellingmistakes onthe userinterfaceAn interfacedesign onlyrequires choiceof colours, fontsand iconsEnsureuserscreateaccountsReflectionsconsist ofexcusesForce loginbut neveruse accountinformationThe interfacematches anexisting appwith controls indifferentpositionsChoice ofcolour schemeis based onpersonalpreferencesSpellingmistakes inthe name ofthe appThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughTask analysisgenerates astructure whichis just the menulayoutEnsure yourapp hasfeatures fromevery other appyou've everusedInherit userinterfacecontrols as partof a screenshotfrom anotherappA teammember isonly asource ofideasBuild yourinterface usingscreenshotsfrom an existingappStart witha loginscreen Walkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyQuestionsslide at theend of thewalkthroughpresentationInterfaceevaluationrequires thatthe user findbugs in theapplicationProvide adetailedinterface tocustomizeyour profileSpend morethan half thewalkthroughdiscussinglogging inDocumentationis independentof the appdesignA team memberindicates(implicitly) thatnobody elsecontributedUser experienceevaluation doesnot mention thespecific interfacedesignSpellingmistakes onthe userinterfaceAn interfacedesign onlyrequires choiceof colours, fontsand iconsEnsureuserscreateaccountsReflectionsconsist ofexcuses

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