Presentation

This page is a public draft.

Its contents may still change.

You will present as a team. You will have 10-12 minutes to present. Divide the time into 3–4 minute segments: one for each student.

Consider presenting the following:

• warn the audience about questions you’ll ask them at the end, e.g.
  • this was really hard for us, we abandoned it. did anyone get it? how?!
• Demonstrate how the application works in the browser:
  • demonstrate its “advanced” functionality, especially persistence, export, import, netwirk request(s), mobile vs. desktop
• Consider walking the class through how to use the app.
• sharing focused excerpts of code that demonstrate reuse, modularization, or other best practices
• sharing your reflections on
  • things that went well or that didn’t
  • successes/challenges with the platform (client-side web)
  • cool/surprising/outrageous things you learned

You must not show your entire code; focus on the most interesting parts. Explain any problems you encountered and how you solved them. Give the audience a sense of what you learned during this project.

Be sure to demo both the “desktop” (large screen) and “mobile” (small screen) layouts of your app. You may use the DevTools to simulate a mobile device, or just resize the browser window, or something else.

The presentation must involve all group members—don’t allow one person to do most of the talking. Practice transitions beforehand so you know how to support each other and tell a cohesive story about your work.

Full Credit only for having a backup recording?

• students should rehearse.
• get full points only for proving it
  • happens to help with unexpected schedule problems