Checkpoint three

Peer evaluation two (two points, graded separately)

  • Click here to complete your peer evaluation
  • If you do not complete peer evaluations for your peers, you will receive a zero (even if you receive outstanding reviews)

Checkpoint Three Assignments (10 points total / 2.5 points each)

Each of the four items below will be graded according to the following scale.

  • 2.5 points: 🔥 1
  • 2 points: 👏 2
  • 1.5 points: 👍 3
  • 1 point: 😐 4
  • .5 points:🤦‍♂️ / 🤦‍♀️ 5
  • 0 points: 👻 6

0. Presentation

  • 3-5 minutes long
  • Any combination of team members may present
  • Slides are required, and their design will influence your grade
  • You should be clearly rehearsed, and we’ll closely evaluate your presentation skills
  • You should present your app’s visual design, give a live demo of your 1.0, and show off your website beta
  • Unless there’s a technical reason not to do so, demo on device, not on simulator
  • For demoing your 1.0, use a user story / narrative to guide what and how you demo
  • Whenever you show screenshots of your app / website, use device frames for your screenshots to ground the images.7

1. 1.0

  • A rough draft of your complete final project. Every screen / interaction / etc. that you anticipate including in your final build should be present in this build in as complete a form as possible. 8
  • While your 1.0s will be evaluated during your presentation only, you must also post a copy of your 1.0 to your website to ensure you’re familiar with that process for your final build

2. Visual design guide

  • Your visual design guide will live as a dedicated page on your project website
  • At a minimum, this should include guidelines and reference files for your logo(s), typefaces, and brand colors, but could also include page templates, screenshots, motion graphics, etc.—essentially, everything related to the style of all components of your project
  • Include easy download links for all visual assets in the guide.
  • In addition to the style guide-like elements above, your guide should also include concise discussion of why your team made the choices it did
  • Be sure to include typographic scale (appropriate font sizes / weights for headers, subheads, body, etc., including as necessary variants for web / mobile / print etc.)
  • Include JPEG / PNG / vector (.eps / .ai) versions of your logos in relevant resolutions (hi-res, low-res, etc.)—make it easy for people who don’t know how to handle images to know which variant to use
  • Submit the link your visual design guide with this Google Form and view work from previous semesters here.

3. Website beta

  • A rough draft of your complete website
  • While not a requirement for the beta, be sure to focus on how your site looks on mobile—this is where the overwhelming share of usage is. You’ll likely need to write / modify media queries to accomplish this.9

  1. Killed it / crushed it / etc. Truly exceptional work. Exceeded expectations.

  2. Solid work! You did a good job and should feel good.

  3. Not bad. A bit rough / weak in some key areas, but all the essentials are there.

  4. Not so hot. You turned it something resembling the assignment, but you should be worried.

  5. Oof. You did…something. But barely.

  6. You didn’t turn in anything at all. Do better.

  7. The pro move: for movies, record your screen, then place that recording on top of the device frame on your slides

  8. From this point, the remainder of your project work for the semester should be focused on polishing what’s present in this build, not on adding features / missing elements.

  9. It’s easy to forget to do this since we design websites on desktops / laptops.