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