I t started as a simple point tracking system that would allow students to earn points, power up their robots, and attack the monster (which was the main goal for each in person class we had). Overtime, the more features I added, the more this system took on shape and personality!
The Face of a Robot
The story is is that each student controls 1 nano bot (located on the teeth of the robot) and the goal is to defeat the virus! The entire main processing frame must be saved..
“I just wanted my students to feel jazzed about going to coding class and feel a sense of teamwork and comraderie.”
figure 1
The EYES of the Robot
The entire application was designed to be a character. The eyes were the first thing I built which added a layer of personality and size. I wanted the robot to feel alive, so I made the eyes responsive to user actions like blinking, sleeping, and displaying different kinds of emotions.
figure 2
The TEETH of the Robot
The teeth (or mouth) of the robot would have these tiny nano bots that the students could control by earning more points during class. They could fix other broken nano bots or attack the computer virus. If the computer virus was destroyed, the class would recieve no homework!
figure 3
FIRST CO-PILOT
I had built designed my initial chatbot in the bottom left panel so that students could receive messages from the robot, but in order to make it interactive, I added a simple AI copilot that would respond to questions and help students navigate the LMS.
figure 4
CO-PILOT VER. 2
The point tracking system was only a piece of the monitoring the entire learning management system. I needed a way to monitor student performance progress by capturing data based on several key coding best practices such as code readability, modularity, and the use of comments.
