Questionsslide at theend of thewalkthroughpresentationReflectionsfocus on thetool used tocreate thewalkthroughEnsureuserscreateaccountsSpend morethan half thewalkthroughdiscussinglogging inA teammember isonly asource ofideasSpellingmistakes inthe name ofthe appAn interfacedesign onlyrequires choiceof colours, fontsand iconsBuild yourinterface usingscreenshotsfrom an existingappDivide thedesign amongstteam membersand each worksindependentlyUser experienceevaluation doesnot mention thespecific interfacedesignThe interfacematches anexisting appwith controls indifferentpositionsSpellingmistakes onthe userinterfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappDocumentationis independentof the appdesignForce loginbut neveruse accountinformationWalkthroughpresentationdoesn't actuallymention theuser interfaceReflectionsconsist ofexcusesA team memberindicates(implicitly) thatnobody elsecontributedStart witha loginscreen Provide adetailedinterface tocustomizeyour profileEnsure yourapp hasfeatures fromevery other appyou've everusedChoice ofcolour schemeis based onpersonalpreferencesInherit userinterfacecontrols as partof a screenshotfrom anotherappInterfaceevaluationrequires thatthe user findbugs in theapplicationTask analysisgenerates astructure whichis just the menulayoutQuestionsslide at theend of thewalkthroughpresentationReflectionsfocus on thetool used tocreate thewalkthroughEnsureuserscreateaccountsSpend morethan half thewalkthroughdiscussinglogging inA teammember isonly asource ofideasSpellingmistakes inthe name ofthe appAn interfacedesign onlyrequires choiceof colours, fontsand iconsBuild yourinterface usingscreenshotsfrom an existingappDivide thedesign amongstteam membersand each worksindependentlyUser experienceevaluation doesnot mention thespecific interfacedesignThe interfacematches anexisting appwith controls indifferentpositionsSpellingmistakes onthe userinterfaceThe quality of theinterface isproportional to thenumber of featuresprovided by theappDocumentationis independentof the appdesignForce loginbut neveruse accountinformationWalkthroughpresentationdoesn't actuallymention theuser interfaceReflectionsconsist ofexcusesA team memberindicates(implicitly) thatnobody elsecontributedStart witha loginscreen Provide adetailedinterface tocustomizeyour profileEnsure yourapp hasfeatures fromevery other appyou've everusedChoice ofcolour schemeis based onpersonalpreferencesInherit userinterfacecontrols as partof a screenshotfrom anotherappInterfaceevaluationrequires thatthe user findbugs in theapplicationTask analysisgenerates astructure whichis just the menulayout

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