-
Notifications
You must be signed in to change notification settings - Fork 11
Assignment #7: Storyboard Roughs
Hooray! It's time to turn your team's plan into sketches. Why sketch? Because this helps you test ideas and catch any flaws in a low-cost way. It's much easier to discard a sketch than a chunk of code.
Mobile-first layout
These sketches will be for the smallest size (mobile).
For every template/view, you'll sketch out (using pencil + paper) wireframes. A minimum of 5 sketches per view is expected, but sketching out more will result in a better end product.
Even if you think an idea will not work, sketch it. Don't worry if they are sloppy or look like stick figures. The goal is to sketch as many ideas as you can and get them out onto paper.
Here's an example of sketches I pulled from various projects.
Reflect on what ideas you came up with. Ask yourself what works and what doesn't for each view. When you've decided on a final layout for each view, sketch them again. Combine them into one section.
Gather all of your sketches. Then, combine these into a single PDF.
Your annotations should sell your work. It should explain things like:
- How did you arrive at this layout?
- What works about the layout you decided?
- What element is this?
- What element is that?
- Why did you put that there?
- What happens when I tap that button?
- Is that a headline?
- What if it's a long headline?
- What else did you try?
- Why didn't you choose that direction?
Upload your final PDF to Slack. Name it A7-Your-Team-Name.pdf.
Points will be deducted for sloppy naming.
Mention @emily and @rob to make sure we give you the 👍
Due: 11:59 p.m. Monday, Oct. 19
Points possible: 20
Resources