Classroom Mode Opens the Door

The first classroom release was about making a live CS session easy to join and easy to follow, using practice mechanics students already understood.

What changed

We introduced live classroom joining, guest-friendly flows, sync between host and players, a battle-style classroom IDE, and shared quiz links. That gave educators a way to bring algorithm questions into a room without asking every student to set up a full account before class could begin.

The early classroom experience reused the strongest parts of the practice product: a clear prompt, an answer surface, visible progress, and immediate feedback.

How a live game runs

A teacher starts a game from a quiz, and the lobby puts a join code on the screen in large type, along with the address where students enter it. A student types the code and a name, joining as a guest under that name if they are not signed in. Each name appears in the lobby as it arrives, and the host starts the game once the room is in.

From there the host's screen sets the pace. Every student sees the same question at the same moment, and nobody moves on until the host does. While a question is open, the host's screen counts submissions against the number of players and says so when everyone has answered. A coding question opens in an editor built like the one in battles, where a student picks a language, runs the code against the question's tests to see which pass, and submits when ready.

When the question closes, the reveal shows how the whole room did. For a multiple choice question, a bar over each option shows how many students chose it, with the correct one highlighted. For a coding question, it counts how many students passed every test and how many submitted, along with the average number of tests passed. A leaderboard follows, and at the end each student sees their final rank and accuracy.

Why it matters

Teaching programming live is hard because the teacher is always balancing two needs, keeping the group moving and noticing who is lost. Most tools choose one side, either hiding the work until after class or creating so much live noise that the teacher cannot act on it.

Classroom is designed for the middle, with enough live signal to guide teaching and enough structure to keep the room sane.

The middle is hard to hold because both demands are live and apply to every student at once. Pause to help the one person who is stuck and you stall the other twenty. Keep the pace and the struggling student quietly falls behind. The reveal helps with that choice. If half the class picked the same wrong option, that is one misconception worth stopping to reteach. If most students submitted code but few passed every test, the edge cases are probably the next thing to go over.

Where it points

This was the beginning of Classroom as a main product lane. The next work is about authoring, replay, debrief, and problem selection so a live session can turn into lasting learning material, and Classroom Grows Into a Live Teaching Surface picks up that thread.