Documentationis independentof the appdesignSpellingmistakes onthe userinterfaceTask analysisgenerates astructure whichis just the menulayoutReflectionsconsist ofexcusesThe interfacematches anexisting appwith controls indifferentpositionsStart witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferencesBuild yourinterface usingscreenshotsfrom an existingappThe quality of theinterface isproportional to thenumber of featuresprovided by theappUser experienceevaluation doesnot mention thespecific interfacedesignA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inQuestionsslide at theend of thewalkthroughpresentationA team memberindicates(implicitly) thatnobody elsecontributedInterfaceevaluationrequires thatthe user findbugs in theapplicationEnsure yourapp hasfeatures fromevery other appyou've everusedForce loginbut neveruse accountinformationEnsureuserscreateaccountsDivide thedesign amongstteam membersand each worksindependentlyProvide adetailedinterface tocustomizeyour profileWalkthroughpresentationdoesn't actuallymention theuser interfaceInherit userinterfacecontrols as partof a screenshotfrom anotherappReflectionsfocus on thetool used tocreate thewalkthroughDocumentationis independentof the appdesignSpellingmistakes onthe userinterfaceTask analysisgenerates astructure whichis just the menulayoutReflectionsconsist ofexcusesThe interfacematches anexisting appwith controls indifferentpositionsStart witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferencesBuild yourinterface usingscreenshotsfrom an existingappThe quality of theinterface isproportional to thenumber of featuresprovided by theappUser experienceevaluation doesnot mention thespecific interfacedesignA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inQuestionsslide at theend of thewalkthroughpresentationA team memberindicates(implicitly) thatnobody elsecontributedInterfaceevaluationrequires thatthe user findbugs in theapplicationEnsure yourapp hasfeatures fromevery other appyou've everusedForce loginbut neveruse accountinformationEnsureuserscreateaccountsDivide thedesign amongstteam membersand each worksindependentlyProvide adetailedinterface tocustomizeyour profileWalkthroughpresentationdoesn't actuallymention theuser interfaceInherit userinterfacecontrols as partof a screenshotfrom anotherappReflectionsfocus 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. Documentation is independent of the app design
  2. Spelling mistakes on the user interface
  3. Task analysis generates a structure which is just the menu layout
  4. Reflections consist of excuses
  5. The interface matches an existing app with controls in different positions
  6. Start with a login screen
  7. An interface design only requires choice of colours, fonts and icons
  8. Spelling mistakes in the name of the app
  9. Choice of colour scheme is based on personal preferences
  10. Build your interface using screenshots from an existing app
  11. The quality of the interface is proportional to the number of features provided by the app
  12. User experience evaluation does not mention the specific interface design
  13. A team member is only a source of ideas
  14. Spend more than half the walkthrough discussing logging in
  15. Questions slide at the end of the walkthrough presentation
  16. A team member indicates (implicitly) that nobody else contributed
  17. Interface evaluation requires that the user find bugs in the application
  18. Ensure your app has features from every other app you've ever used
  19. Force login but never use account information
  20. Ensure users create accounts
  21. Divide the design amongst team members and each works independently
  22. Provide a detailed interface to customize your profile
  23. Walkthrough presentation doesn't actually mention the user interface
  24. Inherit user interface controls as part of a screenshot from another app
  25. Reflections focus on the tool used to create the walkthrough