Setting the Stage for Students
A few days ago, my AP CS Principles students completed a multi-screen app project in the Code.org App Lab environment. I was simply blown away by the creativity of their apps! This is the third year I've taught the Code.org curriculum, and this year I focused more on peer feedback and the iterative process.
We began the lesson by introducing the project - creating an app whose design included at least 4 screens and whose code included event handlers allowing the user to interact with the app. The rubric also laid out the expectations that:
1) The intended purpose of the app is clear.
2) The app is visually appealing and the user interface is intuitive to use.
On the day that the app was due, I asked students to trade their app with a peer, go through the rubric, and give each other constructive feedback based on the rubric. They shared with at least two peers, and then I asked them to modify their app based on the feedback they received. I explained that this version is considered a beta version, and that they would submit the final version the next day.
On the day that the final version was due, students submitted the links to their apps via a Google form, and then I shared the online spreadsheet that listed all of the app project links with all my classes. Along with the link, they included their name and a short description of the app. During class, I asked students to share an app they were really excited about. It was such a pleasure to showcase the apps and a couple times, students spontaneously clapped for the developer of the app! These moments are why I teach.
For this project, I learned to set the stage, and allowed students to inspire and learn from each other.
Here are a couple student examples:
br />
We began the lesson by introducing the project - creating an app whose design included at least 4 screens and whose code included event handlers allowing the user to interact with the app. The rubric also laid out the expectations that:
1) The intended purpose of the app is clear.
2) The app is visually appealing and the user interface is intuitive to use.
On the day that the app was due, I asked students to trade their app with a peer, go through the rubric, and give each other constructive feedback based on the rubric. They shared with at least two peers, and then I asked them to modify their app based on the feedback they received. I explained that this version is considered a beta version, and that they would submit the final version the next day.
On the day that the final version was due, students submitted the links to their apps via a Google form, and then I shared the online spreadsheet that listed all of the app project links with all my classes. Along with the link, they included their name and a short description of the app. During class, I asked students to share an app they were really excited about. It was such a pleasure to showcase the apps and a couple times, students spontaneously clapped for the developer of the app! These moments are why I teach.
For this project, I learned to set the stage, and allowed students to inspire and learn from each other.
Here are a couple student examples:
br />
Comments
Post a Comment