Act II: Web App Pitch #

Act II focuses on planning and outlining a Web Application. Your will need to consider backend architecture and frontend architecture in order to create a comprehensive plan.

[0] Project Overview #

🎨 Design Brief: In this project, you must create a social computing Web App for G6 tutor groups. Students should be able to contribute, interact, view, and/or modify the Database. It is up to your team to decide what the App is its features.

🤔 Here are a few ideas:

• last year’s projects
• fizz or YikYak
• higher/lower game
• list of fun APIs
• lucky draw
• blessings - use emma as the password
• communal Mad Libs, Magic-8 ball, or meme generator

[1] Design Document #

For this project, you will use a Canva white-board to design the frontend and backend of your Web App.

👀 Join the Canva class with this link and find your group’s board.

✏️ You and your teammate(s) must work together to plan the backend and frontend of your web app.

0. project description
1. UML diagram
2. data flow diagram
3. flow chart of user interactioin
4. low-fidelity wireframe of MVP
5. 3-5 success claims of MVP

🔍 A few resources:

• Django Model Field Types
• Google Fonts
• Fontjoy - generates font combinations
• coolors generator
• google color picker
• dribbble

[2] Pitch Presentation #

You will take your polished wireframes and you great web app idea and present it to your peers, teachers, and guests. After your presentation, the audience should understand what your app does, what features it has, and who will use it when it’s finished. This is a valuable opportunity to pitch your idea and receive feedback.

You can find the slides template in your Google Drive. Choose which of your team member’s slides to use and notify a teacher.

Your pitch should include:

• a short description of your idea
• what features your app will have
• images of your wireframes

[3] Assessment #

✅ This project will be assessed on the following criteria:

• Backend Design [3]
  • We can plan the architecture of a Django Model by using appropriate field and methods
  • We can create a clear and accurate data flow diagram to describe how the user interactions with the database
  • We can use descriptive naming conventions for code readability
• Frontend Design [3]
  • We can outline the user flow navigation to ensure a logical user experience
  • We can design a low-fidelity wireframe for each necessary template in the MVP
  • We can include placeholder text or example data from the Model to demonstrate how the design interactions with the backend
• Success Claims [3]
  • We can write success claims that are specific, measurable and testable to evaluate the web app
  • We can write example test cases for each success claim to demonstrate how the claim will be evaluated
• Pitch Presentation [3]
  • We can present the Web App idea in a clear, engaging manner
  • We can design slides that are easy to read and include relevant visual aids
  • We can respond thoughtfully to audience feedback, demonstrating and understanding of their suggestions

For each criteria you will be assessed on a score from 0-3.

• 0 - no evidence of the practice
• 1 - limited evidence of the practice
• 2 - adequate evidence of the practice
• 3 - substantial evidence of the practice

[4] Deliverables #

⚡✨

🗓️ Due Date: 30 April

• The planning document is due at the start of class
• You will pitch your web app during the class

📄 Deliverables

• A Canva document with your Web App planning
• A Google Slides presentation