Updated Unit 4 Released

csdunit4

#1

Hey CS Discoveries Community,

If you attended TeacherCon this last summer, you know that we’ve been plugging away at updates to the second semester of CSD (units 4, 5, and 6). I’m excited to announce that on October 13th we launched the revised version of Unit 4, the Design Process. Based on feedback from out pilot teachers, we reworked this unit with the following goals in mind:

Decrease the required printing - As this is a primarily unplugged unit, we relied heavily on activity guides to support activities and instruction. In order to balance this support with the reality of printing limitations in many schools, we reworked many lessons so that they could be completed without activity guides, or with journals or scrap paper. We opted not to remove activity guides so that teachers who want them can use them, but look out for teaching tips that call out printer-free alternatives.

Better support the transition from paper to digital prototypes - In the later half of chapter 2, students learn to move their paper app prototypes into App Lab. Pilot teachers found that the App Lab lessons focused too much on discrete skills, without scaffolding the actual process of moving a paper prototype into App Lab. We rewrote these lessons such that all of the skill building levels build on a model app and paper prototype. This way students will have completed the entire process of bringing a paper prototype into App Lab before they need to do it with their own app. We’ve also updated some of the instructional levels to reflect improvements in App Lab around importing screens.

App Lab instruction goes too deep - Often we get significant amounts of contradictory feedback from teachers, which requires some tough balancing on our end. This is one case where many teachers told us that the programming we taught in App Lab went deeper than their kids needed to complete the project, or that they even had time to get into. While other teachers found these deeper lessons really useful, we’ve opted to remove this content for now in the interest of making sure that all classrooms can successfully complete the unit. The lesson in which we introduced this content was always intended to be somewhat optional, and we are investigating better methods of providing optional supplemental instruction that don’t make some kids feel like they didn’t learn something they should have. Once we’ve come up with a better plan for presenting this content we’ll bring it back.

I feel confident that the changes we’ve introduced will make this an easier unit to implement, and a really fun one for your students. If you have any your thoughts or ask questions, please share them here. We’ll continue to post updates as we round out the final units of semester 2.

The CSD Team


#2

I have a qauestion about Unit 4 Lesson 13: Linking Screens. Students are trying to use this to combine their screens and they are not able to get the code provided to work (for linking screens). Is there a workaround or suggestion of how each team member can contribute their individual pages to the group project?

Thank you.
Mrs O’Malley
Cedarcrest Middle School
nomalley@bethelsd.org


#3

Did they follow these instructions from Bubble 13 App Project Screen Import:

Each member of your team is going to create their own copy of the app, with all of the team members’ screens imported in. This will be your copy of the app, and the copy that you will start to add code to in the next lesson.

Collect all of the sharing urls for your team’s pages
You can find the share url by going back to the last level of the previous lesson, or by finding the screen in your projects directory
Import each of the screens, one at a time
If you run into an ID error with one of the screens, discuss the issue with the screen’s creator so it can be fixed and imported
Delete the default “screen1”
Set the main screen as the default

If this didn’t work for them there may be a bug and a bug report maybe needed. Please let me know if this didn’t work and I will escalate this to see if we can resolve it.