Divide thedesign amongstteam membersand each worksindependentlyQuestionsslide at theend of thewalkthroughpresentationBuild yourinterface usingscreenshotsfrom an existingappSpend morethan half thewalkthroughdiscussinglogging inEnsureuserscreateaccountsWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedProvide adetailedinterface tocustomizeyour profileTask analysisgenerates astructure whichis just the menulayoutInherit userinterfacecontrols as partof a screenshotfrom anotherappAn interfacedesign onlyrequires choiceof colours, fontsand iconsA team memberindicates(implicitly) thatnobody elsecontributedStart witha loginscreen The quality of theinterface isproportional to thenumber of featuresprovided by theappChoice ofcolour schemeis based onpersonalpreferencesA teammember isonly asource ofideasUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationReflectionsconsist ofexcusesDocumentationis independentof the appdesignReflectionsfocus on thetool used tocreate thewalkthroughThe interfacematches anexisting appwith controls indifferentpositionsForce loginbut neveruse accountinformationSpellingmistakes inthe name ofthe appDivide thedesign amongstteam membersand each worksindependentlyQuestionsslide at theend of thewalkthroughpresentationBuild yourinterface usingscreenshotsfrom an existingappSpend morethan half thewalkthroughdiscussinglogging inEnsureuserscreateaccountsWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedProvide adetailedinterface tocustomizeyour profileTask analysisgenerates astructure whichis just the menulayoutInherit userinterfacecontrols as partof a screenshotfrom anotherappAn interfacedesign onlyrequires choiceof colours, fontsand iconsA team memberindicates(implicitly) thatnobody elsecontributedStart witha loginscreen The quality of theinterface isproportional to thenumber of featuresprovided by theappChoice ofcolour schemeis based onpersonalpreferencesA teammember isonly asource ofideasUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationReflectionsconsist ofexcusesDocumentationis independentof the appdesignReflectionsfocus on thetool used tocreate thewalkthroughThe interfacematches anexisting appwith controls indifferentpositionsForce loginbut neveruse accountinformationSpellingmistakes inthe name ofthe app

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