Wednesday, April 23, 2014
Wednesday, April 2, 2014
References/readings & day by day info for Project 3:
Thursday, April 03
Map making
Someone in America Loves you
The Good SheetDesign Observer
Feltron Annual reports
Good Naming Reference: 5 Naming Styles
A zag statement “Our blank is the only blank that blanks” so that we know how your blank is different from other apps. Print these out with the name. Each on a sheet of paper, big type so we can read from a distance.
Read Experiences Not Objects, Chapter 7 from the Graphic Design Theory Book, by Meredith Davis. Pay close attention to part on Systems and “Changing Notion of Audience.” :)
Tuesday, April 8th
Thursday, April 10
Create at least 8 icon concepts (use these best practices) based on your final name. Use this tutorial to create your icon in a button. Or this one in Photoshop. if you want to work digitally this round.
Create wireframes of user paths • click through pdf (almost like a storyboard of screens)
• place wireframes in a diagram that show how each screen relates to next screen. Work on a 18 x 24 in doc and print (tile)
Map making
Someone in America Loves you
The Good SheetDesign Observer
Feltron Annual reports
Good Naming Reference: 5 Naming Styles
A zag statement “Our blank is the only blank that blanks” so that we know how your blank is different from other apps. Print these out with the name. Each on a sheet of paper, big type so we can read from a distance.
Read Experiences Not Objects, Chapter 7 from the Graphic Design Theory Book, by Meredith Davis. Pay close attention to part on Systems and “Changing Notion of Audience.” :)
Tuesday, April 8th
Thursday, April 10
Create at least 8 icon concepts (use these best practices) based on your final name. Use this tutorial to create your icon in a button. Or this one in Photoshop. if you want to work digitally this round.
Here is some inspiration as well as what sizes your icon should work in. (512px square, 256px, 144px, 11px, 72px, 57px).
Each concept should be it’s own page (pdf) with three key words (that sum up the concept) and a supporting moodboard with color palette.
Tuesday, April 15th
Thursday, April 17th
Refine icon, naming and create first interface prototype.
Homework:
Create 30 versions of your logo and button on the computer.
Print 10 up on three 8.5 x 11 sheets
Print 10 up on three 8.5 x 11 sheets
Create wireframes of user paths • click through pdf (almost like a storyboard of screens)
• place wireframes in a diagram that show how each screen relates to next screen. Work on a 18 x 24 in doc and print (tile)
Tuesday, April 22nd
Determine how many screens you need to design based on a typical user scenario. Use your persona(s) to determine a story (ex. on a hike and checks phone to identify a bird and then checks with message board/map to find any other birds that have been tagged in the area to look for). Remember Story! (beginning, middle and end)
This story will allow you to identify what screens you need to make to communicate that scenario. Once you have determined the screens (which ones, how many), then starting testing your visual concept against those you selected.
Homework:
Finalize your visual concept board and key words :
• color palette, typography, imagery (graphic or photo or both), pattern, textures etc.
This story will allow you to identify what screens you need to make to communicate that scenario. Once you have determined the screens (which ones, how many), then starting testing your visual concept against those you selected.
Homework:
Finalize your visual concept board and key words :
• color palette, typography, imagery (graphic or photo or both), pattern, textures etc.
Upload latest version of button and wireframes to FieldTest.
Refinements to wireframe (navigation and orientation issues based on testing) and apply visual concept to screens.
Refinements to wireframe (navigation and orientation issues based on testing) and apply visual concept to screens.
Thursday, April 24th
Review visual concept applied to screens and trouble shoot any navigation issues. Clickable pdf or FieldTest for class.
Do we know where we are?
Do we know what we can do next?
Is it easy to create a mental model or schema of what the system “looks” like?
Homework:
Refinement to screens.
Sketches for how you will communicate the final prototype.
Do we know where we are?
Do we know what we can do next?
Is it easy to create a mental model or schema of what the system “looks” like?
Homework:
Refinement to screens.
Sketches for how you will communicate the final prototype.
Bring in a storyboard (10-20 frames) to communicate how you will show the features of your app. Use a template if you’d like and bring in on paper, unless you can show on your laptop.
Tuesday, April 29th
No class. Tad is speaking in Cleveland.
FINAL PROJECT DUE WEDNESDAY MAY 7TH AT REVIEW
Process Book Checklist:
Gather for Process book: (no need to over design, but make clean and organized in this order)
1. Word List and/or Attribute List and/or Mind Map
2. Persona (last page of pdf)
3. Diagram(s): Concept Fan 1, Concept Fan 2, Affinity Diagram, 5 whys or Drill Down
4. Scenario (Storyboard Style) or (Map/Gameboard Style)
5. Write a zag statement “Our blank is the only blank that blanks” so that we know how your blank is different from other apps. Print these out with the name. Each on a sheet of paper, big type so we can read from a distance.
6. THREE icons: Each concept should be it’s own page (pdf) with three key words (that sum up the concept) and a supporting moodboard with color palette.
7. Print out templates to draw, cut out and mockup ideas in class on Thursday. In class we will use the templates to make screens, draw, cut out and role play in next class. Brainstorm, Concept, Prototype, Test (Play) and Repeat.
8. Create 30 versions of your logo and button on the computer.
9. Create wireframes of user paths place wireframes in a diagram that show how each screen relates to next screen. Work on a 18 x 24 in doc and print (tile)
10. Finalize your visual concept board and key words • color palette, typography, imagery (graphic or photo or both), pattern, textures etc.
2. Persona (last page of pdf)
3. Diagram(s): Concept Fan 1, Concept Fan 2, Affinity Diagram, 5 whys or Drill Down
4. Scenario (Storyboard Style) or (Map/Gameboard Style)
5. Write a zag statement “Our blank is the only blank that blanks” so that we know how your blank is different from other apps. Print these out with the name. Each on a sheet of paper, big type so we can read from a distance.
6. THREE icons: Each concept should be it’s own page (pdf) with three key words (that sum up the concept) and a supporting moodboard with color palette.
7. Print out templates to draw, cut out and mockup ideas in class on Thursday. In class we will use the templates to make screens, draw, cut out and role play in next class. Brainstorm, Concept, Prototype, Test (Play) and Repeat.
8. Create 30 versions of your logo and button on the computer.
9. Create wireframes of user paths place wireframes in a diagram that show how each screen relates to next screen. Work on a 18 x 24 in doc and print (tile)
10. Finalize your visual concept board and key words • color palette, typography, imagery (graphic or photo or both), pattern, textures etc.
Other references
Subscribe to:
Posts (Atom)