Start witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inThe interfacematches anexisting appwith controls indifferentpositionsDocumentationis independentof the appdesignTask analysisgenerates astructure whichis just the menulayoutQuestionsslide at theend of thewalkthroughpresentationReflectionsconsist ofexcusesDivide thedesign amongstteam membersand each worksindependentlyInherit userinterfacecontrols as partof a screenshotfrom anotherappBuild yourinterface usingscreenshotsfrom an existingappForce loginbut neveruse accountinformationWalkthroughpresentationdoesn't actuallymention theuser interfaceUser experienceevaluation doesnot mention thespecific interfacedesignProvide adetailedinterface tocustomizeyour profileA team memberindicates(implicitly) thatnobody elsecontributedEnsure yourapp hasfeatures fromevery other appyou've everusedThe quality of theinterface isproportional to thenumber of featuresprovided by theappSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferencesReflectionsfocus on thetool used tocreate thewalkthroughEnsureuserscreateaccountsSpellingmistakes onthe userinterfaceStart witha loginscreen An interfacedesign onlyrequires choiceof colours, fontsand iconsInterfaceevaluationrequires thatthe user findbugs in theapplicationA teammember isonly asource ofideasSpend morethan half thewalkthroughdiscussinglogging inThe interfacematches anexisting appwith controls indifferentpositionsDocumentationis independentof the appdesignTask analysisgenerates astructure whichis just the menulayoutQuestionsslide at theend of thewalkthroughpresentationReflectionsconsist ofexcusesDivide thedesign amongstteam membersand each worksindependentlyInherit userinterfacecontrols as partof a screenshotfrom anotherappBuild yourinterface usingscreenshotsfrom an existingappForce loginbut neveruse accountinformationWalkthroughpresentationdoesn't actuallymention theuser interfaceUser experienceevaluation doesnot mention thespecific interfacedesignProvide adetailedinterface tocustomizeyour profileA team memberindicates(implicitly) thatnobody elsecontributedEnsure yourapp hasfeatures fromevery other appyou've everusedThe quality of theinterface isproportional to thenumber of featuresprovided by theappSpellingmistakes inthe name ofthe appChoice ofcolour schemeis based onpersonalpreferencesReflectionsfocus on thetool used tocreate thewalkthroughEnsureuserscreateaccountsSpellingmistakes onthe userinterface

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