Students investigate how an Arduino R4 WiFi can address a real school or community problem by designing and building a functional device over four weeks. They learn to code sketches that use events, sensors, outputs, modules, libraries, and Wi-Fi/app connections while comparing the R4’s capabilities to the R3 to make informed design choices. Through iterative testing, peer critique on a portfolio, and revision based on user feedback, they develop a prototype and communicate their process and results in a class presentation. The experience builds content expertise, collaboration, communication, self-direction, and problem solving through an independent project and portfolio grounded in authentic use.

Students will program the Arduino R4 WiFi to read sensors, control outputs, and use events, logic, procedures, and libraries to build a working device for a real school or community need. They will compare the R4 WiFi to the R3, connect the board to an app or networked interface, and choose features that best fit their design problem. Students will use an engineering design process to prototype, test, collect data, and revise their device based on evidence and peer feedback documented in a project portfolio. They will communicate their learning through code snapshots, design notes, reflections, and a final class presentation of an independent project.

Students will create a series of working mini-builds with the Arduino R4 WiFi, such as sensor-input/output tests, app-connected prototypes, and comparison experiments showing what the R4 can do that the R3 cannot. Throughout the project, they will maintain a digital portfolio with design notes, code snapshots, wiring diagrams, test data, peer feedback, and revision reflections. In teams or independently, they will build a final functional device that addresses a real school or community problem using sensors, outputs, basic logic, and, when appropriate, Wi-Fi or app connectivity. The culminating products are the finished device, a documented portfolio, and a class presentation that explains the problem, the design process, the code, testing results, and improvements made after critique.

Open with an “R4 Reveal Night” experience: show a short video of smart devices in action, then run a live demo of the Arduino R4 WiFi reading a sensor and sending data to the app to trigger an output. Invite students to rotate through quick hands-on stations where they test one R4 feature the R3 cannot do as easily, such as Wi-Fi connectivity or app-based control, and capture first impressions in a design notebook. Close with a class brainstorm of real school or community problems the device could address, then have teams choose one problem to investigate through a four-week prototype challenge.

End with a class showcase where each team gives a 3–5 minute presentation to the class and demonstrates a working Arduino R4 WiFi device that addresses a real school or community problem. Students should display their portfolio alongside the prototype, including design notes, code snapshots, sensor/app connections, test data, revisions from peer feedback, and an explanation of why they used R4 features such as Wi-Fi or added processing power. Invite classmates, school staff, and a few authentic users to ask questions and give feedback on usefulness, usability, and next steps. Close with a brief reflection round where students share what they changed through critique, what their device can do, and what they would improve with more time.