Inherit userinterfacecontrols as partof a screenshotfrom anotherappAn interfacedesign onlyrequires choiceof colours, fontsand iconsChoice ofcolour schemeis based onpersonalpreferencesProvide adetailedinterface tocustomizeyour profileSpellingmistakes inthe name ofthe appStart witha loginscreen Documentationis independentof the appdesignWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceA team memberindicates(implicitly) thatnobody elsecontributedThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughDivide thedesign amongstteam membersand each worksindependentlyBuild yourinterface usingscreenshotsfrom an existingappTask analysisgenerates astructure whichis just the menulayoutThe interfacematches anexisting appwith controls indifferentpositionsSpend morethan half thewalkthroughdiscussinglogging inA teammember isonly asource ofideasEnsureuserscreateaccountsUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationQuestionsslide at theend of thewalkthroughpresentationReflectionsconsist ofexcusesEnsure yourapp hasfeatures fromevery other appyou've everusedForce loginbut neveruse accountinformationInherit userinterfacecontrols as partof a screenshotfrom anotherappAn interfacedesign onlyrequires choiceof colours, fontsand iconsChoice ofcolour schemeis based onpersonalpreferencesProvide adetailedinterface tocustomizeyour profileSpellingmistakes inthe name ofthe appStart witha loginscreen Documentationis independentof the appdesignWalkthroughpresentationdoesn't actuallymention theuser interfaceSpellingmistakes onthe userinterfaceA team memberindicates(implicitly) thatnobody elsecontributedThe quality of theinterface isproportional to thenumber of featuresprovided by theappReflectionsfocus on thetool used tocreate thewalkthroughDivide thedesign amongstteam membersand each worksindependentlyBuild yourinterface usingscreenshotsfrom an existingappTask analysisgenerates astructure whichis just the menulayoutThe interfacematches anexisting appwith controls indifferentpositionsSpend morethan half thewalkthroughdiscussinglogging inA teammember isonly asource ofideasEnsureuserscreateaccountsUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationQuestionsslide at theend of thewalkthroughpresentationReflectionsconsist ofexcusesEnsure yourapp hasfeatures fromevery other appyou've everusedForce loginbut neveruse accountinformation

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