A8: Show & Tell; Extra Credit Team

Prepare your final presentation: a 30-second design pitch with a summary slide and a 1-minute walkthrough demonstrating your prototype. Submit your pitch and walkthrough together as a single 90-second video (pitch then demo). Finally, polish your prototype: clean up the interface design and squash usability bugs.

Pitch should cover 1) What is the problem? 2) Why doesn’t the obvious thing available today address it? 3) What is one concrete feature of your app that achieves it. (Avoid laundry lists: “it slices, it dices, it’s a TV remote!” Emphasize a concrete example over vague flowery language.)

Submit a PDF with your video, script, and slide. This assignment is 19 points + 5 possible additional points for extra credit.

Evaluation Rubric

    Pitch
  1. Script submitted; fits in 30 seconds.
  2. Pitch that opens video is well-rehearsed, audible, and uses the time well.
  3. Pitch conveys clear point of view, user need (what a goal and why is the best way to do that today lacking), and how the prototype meets them. (Don't just assert that it's awesome.)
  4. Pitch has a creative hook that lures viewers in. This might be an example or scenario.

    5. Slide
  5. Slide image uploaded to PUBLICLY available google drive link (1920x1080 JPG or PNG) and the corresponding link pasted in the Gradescope submission; slide includes your app's name. (If the link is not UNIVERSALLY/PUBLICLY accessible by due date and grader access is denied, no credit will be given.)
  6. Contains one or two screens of the user interface, illustrating the prototype's functionality
  7. Slide has a high-level overview of the prototype, and is not cluttered by having too many words or too much detail

    8. Walkthrough
  8. Write and submit the script for 1-minute walkthrough of your prototype
  9. 1-min walkthrough in video verbally & visually conveys motivation for design, and how design accomplishes POV (better than current options)
  10. Walkthrough fluidly demonstrates use of the prototype in a logical and sequential manner in strictly less than one minute

    11. Post Mortem
  11. Write five to six sentences describing what you learned from working with your team, what you would do differently if you did it all again, mistaken and successful planning choices you made
  12. Final prototype meets the functionality and aesthetic requirements from all previous assignments
  13. Final prototype is bug free and has a clear interaction flow, with no major heuristic violations
  14. There are no spelling or grammatical errors in the slide, pitch, walkthrough, and prototype

    15. Development Plan
  15. A clickable or easily typed UNIVERSALLY/PUBLICLY ACCESSIBLE link, or a readable, properly oriented, and complete snapshot of your dev plan. Make sure the grader has access by the deadline. All tasks are actionable, prioritized, assigned an owner, and given a time estimate. In your comments column, identify tasks that were newly added or removed/updated. Includes a sum of the expected and actual number of hours for each teammate. Outliers should be justified

    16. Submit
  16. Submit a clickable or easily typed link to your final prototype of the form “a8-projectname.herokuapp.com”. If your prototype is changed post-deadline and before grading is completed, you will receive no credit for the assignment
  17. Submit a clickable or easily typed link to your project repository on GitHub. Make sure the grader has access by the deadline. No access = no credit. If your code is changed post-deadline and pre-grading, you will not receive credit.
  18. Universally accessibly/PUBLIC links to each of the following items: your video and your slide
  19. Make ixd@ucsd.edu a collaborator on Heroku so that we have access to your deployment history

Extra Credit Assignments

You have two opportunities for extra credit. You will earn one point for each rubric item met. Feel free to do as many as you wish. They are all group extra credit opportunities.

Revisit Inspiration

Before the implementation of your prototype, you compiled a list of inspirations. Since then, your prototype has probably made many twists, turns, and transformations, and is no longer recognizable as the idea that you started off with. To prepare for your final presentation, update your knowledge of related projects. Related projects can be existing applications, artifacts, products, or services that relate to your concept. Here, web search is your friend (potentially useful sites include Google, Google Scholar, the ACM Digital Library, TechCrunch, Engadget...). Pick five interesting projects that a juror is mostly like to ask you "How are you different from _____?" In some cases, this might be a similar service like another to-do list, photo-sharing app, or party-finder. In other cases, it might be repurposing general services like Google Docs or Twitter.

For each project, write a few detailed sentences that would answer juror questions like, "Why would people use your application instead of _____? In what situations would people use/do _____ instead of your application?"

  1. Five projects are found with explanations of relevance and differences provided.
  2. Provided explanations are well-thought out and thorough as to why each project is relevant, and how they differ from the team's prototype.

Publicize Your App

You have done an amazing job prototyping and evaluating your application, and now it's time to see what the world thinks. Launch your app to the public. This means advertising on Google or Facebook, creating a Fan Page on Facebook, posting in the Mozilla Marketplace, or announcing on your app on social networks like Facebook and Twitter. (Posting to a UCSD mailing list is a good start, but think broader.) These are all just suggestions for what you might do. The goal of this extra credit opportunity is to expose your app to the public by any method you wish to use.

Submit any materials that show that you have widely advertised your application. This can include email receipts, screenshots of the app on a app store, or URLs to app listings. Also submit any materials necessary to show that people outside of this class and the university have started using your application as a direct result of your launch. Since this will differ between groups, we will leave up to you to decide what exactly is necessary to be submitted. The only requirement is to provide sufficient proof to show that you have launched your app to the public and that people have started using it.

  1. Evidence is provided of the prototype's accessibility and more than a couple strangers (who are not people you know or in this class) have found your app and started using it.
  2. Evidence is provided that the prototype was widely noticed on social media.
  3. Submission includes longitudinal data (100+ users over 1+week) on Woopra/Google Analytics.

Student Examples

Here are some randomly selected examples from prior years. Note assignments change from year to year, so use these examples as a reference, see where they succeed/breakdown, and make sure your final submissions adhere to the rubric for this year.

Slides: (1) (2) (3)

Walkthroughs: (1) (2)

Final pitches: (1)