Start witha loginscreen A team memberindicates(implicitly) thatnobody elsecontributedQuestionsslide at theend of thewalkthroughpresentationEnsure yourapp hasfeatures fromevery other appyou've everusedChoice ofcolour schemeis based onpersonalpreferencesForce loginbut neveruse accountinformationProvide adetailedinterface tocustomizeyour profileSpellingmistakes inthe name ofthe appReflectionsconsist ofexcusesEnsureuserscreateaccountsSpend morethan half thewalkthroughdiscussinglogging inAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes onthe userinterfaceThe interfacematches anexisting appwith controls indifferentpositionsReflectionsfocus on thetool used tocreate thewalkthroughWalkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyDocumentationis independentof the appdesignTask analysisgenerates astructure whichis just the menulayoutUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasThe quality of theinterface isproportional to thenumber of featuresprovided by theappBuild yourinterface usingscreenshotsfrom an existingappInherit userinterfacecontrols as partof a screenshotfrom anotherappStart witha loginscreen A team memberindicates(implicitly) thatnobody elsecontributedQuestionsslide at theend of thewalkthroughpresentationEnsure yourapp hasfeatures fromevery other appyou've everusedChoice ofcolour schemeis based onpersonalpreferencesForce loginbut neveruse accountinformationProvide adetailedinterface tocustomizeyour profileSpellingmistakes inthe name ofthe appReflectionsconsist ofexcusesEnsureuserscreateaccountsSpend morethan half thewalkthroughdiscussinglogging inAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes onthe userinterfaceThe interfacematches anexisting appwith controls indifferentpositionsReflectionsfocus on thetool used tocreate thewalkthroughWalkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyDocumentationis independentof the appdesignTask analysisgenerates astructure whichis just the menulayoutUser experienceevaluation doesnot mention thespecific interfacedesignInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasThe quality of theinterface isproportional to thenumber of featuresprovided by theappBuild yourinterface usingscreenshotsfrom an existingappInherit userinterfacecontrols as partof a screenshotfrom anotherapp

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