Why we built Apollo

Every one of us has sat in the same lecture. The lights dim, a slide deck appears, and for the next fifty minutes a single person talks at a room that has quietly stopped participating. The slides are static. The questions go unasked. The good ideas in the room never make it out of anyone's head.

We did not think the problem was the teacher. We thought the problem was the tool. A slide deck is a broadcast medium in a room that should be a conversation.

What we actually wanted

We wanted the projector to feel less like a television and more like a shared surface — something the whole room touches at once.

• Live, not recorded. The lecture is happening now, and everyone is in it.
• Two-way, not one-way. A question, a poll, a reaction should travel from any seat back to the front in an instant.
• Playful, not procedural. Participation should feel like a game you want to play, not a form you have to fill in.

None of that replaces the teacher. It amplifies them. The teacher is still the conductor; Apollo just widens the channel between what they mean and what the room understands.

The one rule we keep coming back to

A good lecture does not transmit information. It gets a room to think about the same thing at the same time.

Everything in Apollo is a test of that sentence. If a feature makes the room think together, it stays. If it just adds a dashboard, it goes.

Where this blog goes

This is where we will write about the decisions behind the product — why the realtime layer looks the way it does, what we learned watching real lectures, and the things we tried that did not work. Same format as our lecture notes, because we liked it too much not to reuse it.

Thanks for reading. The next one is about the part that has to feel instant.