An affordance is some characteristic of an object that communicates how it is to be operated.
A keyhole in a lock tells me that I need a key and where to insert it. A handle on a fridge tells me how to pull it. A bottlecap on a bottle of beer tells me something. But does it tell me to use a bottle opener or just unscrew it?
With this context, look around your daily world (room, office, campus) for affordances everywere. Find and photograph a few examples where (visible) affordances were absent, or communicated the wrong thing. Deliverable: Post your photos to Latte with commentary.
Practice Paper Prototyping and developing a user experience flow chart.
Once everyone has read the above articles and thought about them, try to apply what you read about. With your team, develop a set of single screen paper prototypes connected by arrows that indicate when a user action or event leas to another screen or page. I refer to this as your application process flow.
Focus more on the connections between the screens than making super detailed screens. Use separate sheets of paper, one for each screen with indications of how you get to another screen. I discourage you from using html or other tools because you are always better off doing a sketch on paper before going to any tools.
Spend 1-2 hours as a team, divide up the work and come up with a process flow for your app. You don’t need to do more than 10 pages. Tape them to a whiteboard, draw the lines on the board.
Team Deliverable: Submit one or more images with the result of your work. You can use your smartphone to just take pictures. But make shure they are legible!!! Because we will look at them together in class.