C

Classroom 2.0

An interactive virtual classroom desktop app that covers all the problems faced by teachers as well as students. An app where students can experience a near to offline classroom.

The problem Classroom 2.0 solves

We intend to solve the interactive issues of the present online classroom.
From the teacher's side we have features that enables a teacher to lock the screens of the students while taking class. When a classroom is locked, no student can access other tabs on their desktop. To measue the attentiveness, teachers can give out pop-up questions which the students have to answer and the teacher gets a report of the same. Teachers get an attendance report at the end of the class. This report contains the percentage of time each student has spent in the class. These features help the teacher take on a smooth class without any difficulty.

For the students, each student can choose a bench they want to occupy, just like how you walk into a real life classroom and sit. Here on the seats screen, if we hover over them, we can see who has occupied the seat. The bench partners will be on a voice channel throughout the class. Here they can discuss, solve doubts and have a conversation with their partner just like in a real classroom. The students can also converse with the nearby benches if they wish to. However, to avoid ruckus, there is a time limit for the above and if exceeded the student falls back to the bench voice channel and the teacher gets a notification. Students can give out reactions in the chat box making the class a more lively session. This eliminates the main problem of the lack of peer interactivity in a classroom.

Challenges we ran into

Poor network connection resulting in meeting hold ups.
Initially, most of the team members were unfamiliar with the technologies used.
We ran into a lot of bugs which ate up a huge chunk of our time.
When the idea was implemented, there were a lot of questions raised when it was discussed among ourselves.

We took our time in learning and understanding the topics we were weak in. We made sure we understood everything before moving on further. When the collective effort of the team came out, we were able to handle the bugs more efficiently. We were able to structure the idea properly after a number of discussions and meetups.

Discussion