EnsureuserscreateaccountsForce loginbut neveruse accountinformationDocumentationis independentof the appdesignThe interfacematches anexisting appwith controls indifferentpositionsReflectionsfocus on thetool used tocreate thewalkthroughA team memberindicates(implicitly) thatnobody elsecontributedChoice ofcolour schemeis based onpersonalpreferencesAn interfacedesign onlyrequires choiceof colours, fontsand iconsInherit userinterfacecontrols as partof a screenshotfrom anotherappA teammember isonly asource ofideasEnsure yourapp hasfeatures fromevery other appyou've everusedProvide adetailedinterface tocustomizeyour profileBuild yourinterface usingscreenshotsfrom an existingappTask analysisgenerates astructure whichis just the menulayoutQuestionsslide at theend of thewalkthroughpresentationSpellingmistakes inthe name ofthe appWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappSpend morethan half thewalkthroughdiscussinglogging inDivide thedesign amongstteam membersand each worksindependentlyInterfaceevaluationrequires thatthe user findbugs in theapplicationReflectionsconsist ofexcusesUser experienceevaluation doesnot mention thespecific interfacedesignStart witha loginscreen EnsureuserscreateaccountsForce loginbut neveruse accountinformationDocumentationis independentof the appdesignThe interfacematches anexisting appwith controls indifferentpositionsReflectionsfocus on thetool used tocreate thewalkthroughA team memberindicates(implicitly) thatnobody elsecontributedChoice ofcolour schemeis based onpersonalpreferencesAn interfacedesign onlyrequires choiceof colours, fontsand iconsInherit userinterfacecontrols as partof a screenshotfrom anotherappA teammember isonly asource ofideasEnsure yourapp hasfeatures fromevery other appyou've everusedProvide adetailedinterface tocustomizeyour profileBuild yourinterface usingscreenshotsfrom an existingappTask analysisgenerates astructure whichis just the menulayoutQuestionsslide at theend of thewalkthroughpresentationSpellingmistakes inthe name ofthe appWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappSpend morethan half thewalkthroughdiscussinglogging inDivide thedesign amongstteam membersand each worksindependentlyInterfaceevaluationrequires thatthe user findbugs in theapplicationReflectionsconsist ofexcusesUser experienceevaluation doesnot mention thespecific interfacedesignStart witha loginscreen 

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