Task analysisgenerates astructure whichis just the menulayoutSpend morethan half thewalkthroughdiscussinglogging inThe interfacematches anexisting appwith controls indifferentpositionsInherit userinterfacecontrols as partof a screenshotfrom anotherappQuestionsslide at theend of thewalkthroughpresentationBuild yourinterface usingscreenshotsfrom an existingappA team memberindicates(implicitly) thatnobody elsecontributedEnsureuserscreateaccountsAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes inthe name ofthe appUser experienceevaluation doesnot mention thespecific interfacedesignProvide adetailedinterface tocustomizeyour profileStart witha loginscreen Spellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedReflectionsfocus on thetool used tocreate thewalkthroughForce loginbut neveruse accountinformationThe quality of theinterface isproportional to thenumber of featuresprovided by theappA teammember isonly asource ofideasWalkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyInterfaceevaluationrequires thatthe user findbugs in theapplicationChoice ofcolour schemeis based onpersonalpreferencesDocumentationis independentof the appdesignReflectionsconsist ofexcusesTask analysisgenerates astructure whichis just the menulayoutSpend morethan half thewalkthroughdiscussinglogging inThe interfacematches anexisting appwith controls indifferentpositionsInherit userinterfacecontrols as partof a screenshotfrom anotherappQuestionsslide at theend of thewalkthroughpresentationBuild yourinterface usingscreenshotsfrom an existingappA team memberindicates(implicitly) thatnobody elsecontributedEnsureuserscreateaccountsAn interfacedesign onlyrequires choiceof colours, fontsand iconsSpellingmistakes inthe name ofthe appUser experienceevaluation doesnot mention thespecific interfacedesignProvide adetailedinterface tocustomizeyour profileStart witha loginscreen Spellingmistakes onthe userinterfaceEnsure yourapp hasfeatures fromevery other appyou've everusedReflectionsfocus on thetool used tocreate thewalkthroughForce loginbut neveruse accountinformationThe quality of theinterface isproportional to thenumber of featuresprovided by theappA teammember isonly asource ofideasWalkthroughpresentationdoesn't actuallymention theuser interfaceDivide thedesign amongstteam membersand each worksindependentlyInterfaceevaluationrequires thatthe user findbugs in theapplicationChoice ofcolour schemeis based onpersonalpreferencesDocumentationis independentof the appdesignReflectionsconsist ofexcuses

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