Choice ofcolour schemeis based onpersonalpreferencesStart witha loginscreen A team memberindicates(implicitly) thatnobody elsecontributedDivide thedesign amongstteam membersand each worksindependentlyDocumentationis independentof the appdesignSpellingmistakes inthe name ofthe appThe interfacematches anexisting appwith controls indifferentpositionsAn interfacedesign onlyrequires choiceof colours, fontsand iconsInterfaceevaluationrequires thatthe user findbugs in theapplicationBuild yourinterface usingscreenshotsfrom an existingappThe quality of theinterface isproportional to thenumber of featuresprovided by theappTask analysisgenerates astructure whichis just the menulayoutProvide adetailedinterface tocustomizeyour profileUser experienceevaluation doesnot mention thespecific interfacedesignA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inQuestionsslide at theend of thewalkthroughpresentationSpellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedWalkthroughpresentationdoesn't actuallymention theuser interfaceForce loginbut neveruse accountinformationReflectionsfocus on thetool used tocreate thewalkthroughReflectionsconsist ofexcusesInherit userinterfacecontrols as partof a screenshotfrom anotherappEnsureuserscreateaccountsChoice ofcolour schemeis based onpersonalpreferencesStart witha loginscreen A team memberindicates(implicitly) thatnobody elsecontributedDivide thedesign amongstteam membersand each worksindependentlyDocumentationis independentof the appdesignSpellingmistakes inthe name ofthe appThe interfacematches anexisting appwith controls indifferentpositionsAn interfacedesign onlyrequires choiceof colours, fontsand iconsInterfaceevaluationrequires thatthe user findbugs in theapplicationBuild yourinterface usingscreenshotsfrom an existingappThe quality of theinterface isproportional to thenumber of featuresprovided by theappTask analysisgenerates astructure whichis just the menulayoutProvide adetailedinterface tocustomizeyour profileUser experienceevaluation doesnot mention thespecific interfacedesignA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inQuestionsslide at theend of thewalkthroughpresentationSpellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedWalkthroughpresentationdoesn't actuallymention theuser interfaceForce loginbut neveruse accountinformationReflectionsfocus on thetool used tocreate thewalkthroughReflectionsconsist ofexcusesInherit userinterfacecontrols as partof a screenshotfrom anotherappEnsureuserscreateaccounts

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