Guided Project / Session 5 (Age 11-14 Teams)

Note: If you didn't have time for sharing during session 4, be sure to do this now .

Checking our Progress

Before students move onto the next set of requirements, they should finish up the first set of requirements. If they're struggling with finishing the requirements, have a conversation with them to see if they can figure out what's holding them up. If they're putting forth the effort but are struggling to make it work, what have they tried? Have they tried asking someone else who did get it to work?

Another issue that can come up is spending too much time on things that aren't essential to the main requirements. For example, if they might be spending too much time picking background images for each quiz question, or maybe they're trying to come up with more quiz questions than they initially need. The key here is to get the student to think about how they're spending their time on their app.

Try using the "Socratic Method" as much as possible when helping students troubleshoot these issues (ie, ask them open-ended questions to guide their thinking).

New requirements

Intermediate: Different Responses on Final Screen

• At the end of the quiz, show 3 different messages based on how well the user did. For example:
  • If they got all questions right, show "Perfect!"
  • If they scored 7 or more, show "Good job!"
  • If they scored less than 7, show "Better luck next time!"

This requirement requires the use of conditions. There are some great resources on Code.org to help with learning conditions in app lab. It's ok to have everyone pause their work to watch these videos together, regardless of where they are in their project. See Conditions in the student guide for links to videos and activities learn more about conditions.

Advanced: Make a leaderboard

• Ask the user to enter their initials, and add them to a "leader board" database.
• Show the leaderboard with the highest-scoring player at the top.

This is recommended only for students that need an additional challenge beyond the previous requirements. To build your leaderboard screen, you can have a screen with 10 rows of text labels, and then set those text labels programmatically to show the top 10 players. To learn more about how you might do this, you can look at the code.org video library under "loops and arrays" and "processing arrays of data". There are also links to practice activities next to each video on the video library page.