Day 4 Instructional Procedures

1. Starter – Have students explore two new careers from the Career Links Sheet and fill in the Career Notes Worksheet.
2. Introduce the day’s objective—to understand user interfaces and practice testing one with a paper prototype. Present and discuss the User Interfaces Slides.
3. Review key vocabulary: prototype, user interface, and constructive feedback. Clarify these using examples from familiar apps.
4. Play the “What’s for Lunch?” Prototype Test Video to model how paper prototype testing works.
5. Organize students into pairs. Assign one student as the “computer” and the other as the “user.” Provide each pair with a set of User Interface Screen Cards, one Activity Guide: User Testing (Computer), and one Activity Guide: User Testing (User).
6. Demonstrate how the “computer” presents the User Interface Screen Cards in response to user input while the “user” records missing actions or unclear screens in their Activity Guide. Check for understanding before pairs begin.
7. Monitor pairs as they complete the Activity Guides, prompting students to give clear and constructive feedback to improve the interface design.
8. Invite each pair to share one user interface issue they discovered and how they would fix it. Record examples on the board.
9. Facilitate a whole-class reflection summarizing common challenges and effective design ideas identified during testing.
10. Collect the completed Activity Guides and User Interface Screen Cards. Conclude by previewing that next class students will begin designing their own paper prototypes for testing.

Day 5 Instructional Procedures

1. Starter – Have students explore two new careers from the Career Links Sheet and fill in the Career Notes Worksheet.
2. Explain that students will now apply what they learned by creating their own paper prototype for an app idea.
3. Distribute the Project Guide: Paper Prototype and direct teams to complete pages 1–3. Provide notecards and drawing supplies for sketching the initial interface screens.
4. Circulate to guide teams in making their designs clear, consistent, and user-friendly. Encourage labeling and logical screen flow as they use their drawing supplies.
5. With a few minutes left, have students clean up and return the drawing supplies. Collect the notecards and Project Guides: Paper Prototype for safekeeping.
6. If time allows, preview that next class will involve finalizing screens and testing prototypes with another team.

Day 6 Instructional Procedures

1. Begin by having teams gather their materials—their Project Guide: Paper Prototype, User Interface Screen Cards, and drawing supplies—and prepare to continue work.
2. Explain that teams will finalize their User Interface Screen Cards and then test their prototypes with another group. Allow time for teams to complete unfinished designs.
3. Direct teams to page 4 (Part 2) of the Project Guide: Paper Prototype and have them develop five test cases for another group to try.
4. Pair teams for testing and review the testing protocol: one team acts as the “computer” while the other records “what I tried” and “my reaction” for each test case on the partner’s Project Guide: Paper Prototype. After one round, teams switch roles.
5. Signal the end of testing and guide teams to complete the reflection on page 5 of the Project Guide: Paper Prototype, identifying what worked, what didn’t, and what they would improve.
6. Collect the completed Project Guides, User Interface Screen Cards, and drawing supplies as the exit ticket for the day.

Instructional Procedures

1. Starter – Have students explore two new careers from the Career Links Sheet and fill in the Career Links Worksheet.
2. Introduce the purpose of the lesson—to shift focus from developing app features to understanding the business aspects of launching an app, creating a professional brand, and generating revenue. Explain that students will complete three short assignments that will later contribute to their final presentation and app identity.
3. Explain that each team member will take responsibility for one assignment, but all should collaborate and approve each other’s work to ensure consistency across their project.
   
   1. One member will work on the Marketing Team Presentation Template.
   2. One member will collect research using the Market Research Worksheet.
   3. One member will design a logo or icon using the App Icon Design Worksheet.
4. Briefly review each of the three assignments so students can decide which one they want to lead. Provide a short overview and clarify expectations before teams begin.
   
   1. Walk through the Marketing Team Presentation Template and review what information belongs on each slide.
   2. Review the Market Research Worksheet and discuss how to find credible information about similar apps and audiences.
   3. Review the App Icon Design Worksheet and show examples of effective, recognizable app icons.
5. As teams work, remind them to think about how they can present their ideas creatively to a public audience. Encourage originality and a clear connection between the app’s concept, branding, and presentation style.
6. Remind students that this is the only class period dedicated to these three assignments. The marketing presentations will be presented in Milestone 5 to a public audience. If teams need additional time, they will need to finish outside of class. All three assignments are due at the end of the project.

Day 8 Instructional Procedures

1. Tell students that the Code.org Intro to App Lab Tutorial is designed to quickly introduce them to App Lab. Explain that they will learn to create and control buttons, text, images, sounds, and screens to emulate a phone app. At the end, they can extend their example app to reflect their paper prototype app.
2. Review vocabulary for the day: app element, properties (design), interactive app.
3. Have students log in to Code.org. The Code.org Intro to App Lab Tutorial should appear on their dashboard if assigned by the teacher.
4. Have students begin coding by working through as many levels as time allows. They should complete at least levels 1–13. Students should work with their group but each creates their own copy since real-time collaboration is not available.

Day 9 Instructional Procedures

1. Starter – Students continue the Code.org Intro to App Lab Tutorial, picking up near level 15. Use a slide or board message to signal readiness immediately after attendance.
2. Once students finish the example app at level 14, instruct them to alter it to mirror their paper prototype app (level 15).
3. Have students publish completed work as a shared link to submit to the teacher or share with classmates and parents.
4. Direct teams to use the remaining time to prepare and practice their presentations.

Instructional Procedures

1. Starter – Have students evaluate themselves and their teammates in areas of soft skills and participation using the App Design Presentation Rubric.
2. Have students share a link to their Code.org app on slide 8 of the Marketing Team Presentation Template. If a group did not finish, they should write a message stating they will share their paper app instead.
3. Choose one of the following presentation options:
   • App Expo
     
     1. Teams plan an App Expo so others outside of class can hear their marketing presentations and try their paper or digital apps.
     2. Students complete the Team Member Evaluation either before or after the Expo, depending on timing.
     3. Students decide where the Expo will take place:
        
        • During class with other classes invited – Students load their apps or prepare paper apps. Visitors walk around to try them. The App Design Presentation Rubric can be adjusted for this format so visitors provide feedback on what parts of the presentation they engage with.
        • During lunch or before/after school – Students set up tables and Chromebooks in a visible area (e.g., cafeteria). They prepare apps and signs to draw interest. Visitors explore presentations and apps. The App Design Presentation Rubric can be adjusted accordingly.
        • At night during a school/community event – Students set up tables or a lab space and prepare apps and signs. Visitors listen to presentations and try apps. The App Design Presentation Rubric can be adjusted accordingly.
   • Guest Panel Presentation
     
     1. Teams present to a guest panel (teachers, administrators, counselors, etc.).
     2. Each team has 4–5 minutes to present their marketing presentation and provide a quick demo of their app.
     3. Panel members use the App Design Presentation Rubric to assess the presentations.
     4. Rotate through until all groups have presented.
     5. After presentations, students complete the Team Member Evaluation to reflect on their own and their teammates’ contributions.
4. Use the scores and feedback from the Team Member Evaluations and the App Design Presentation Rubrics to complete the App Design Project Rubric.
5. Have students fill in the Fillable Career Grid with careers from the clusters explored in this plan. If students need ideas, provide examples from Connections → Related Career Opportunities. Students can use the career information websites for details like education and salary. You can also show them the Example Career Grid (Product Design & Manufacturing).