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