Inspiration
Have you ever been in the middle of a presentation confused on how to change slides? “Who’s going to go up to the computer?”, “I don’t know when your part ends!”, “this is completely ruining our presentation” These are all questions we as high schoolers panic about when we’re going up to present. The flow of the presentation is disrupted by technical interruptions and there is a distracting bustle of students up front. Time is being wasted and us high schoolers have to endure public speaking for even longer! :( There has to be a better way to present! For this reason, we decided to create Clide!
What it does
Instead of needing to switch presentations and lean over to hit the next button on the keyboard, the process is simple: students open our website on their mobile devices and upload their presentations. The teacher chooses a presenter and the interface on their device turns into a clicker that moves the presentation back or forward. Members of the audience can join the presentation and give supportive reactions! This encourages positive interactions between students and creates a more fluid process for everyone.
How we built it
A lack of sleep, really. We started off by brainstorming different features to implement. Then, we decided on tasks before executing things. Our website uses Svelte and Node.js, and uses a websocket communication layer.
Challenges we ran into
- concurrency (turns out this one's famously hard)
- state synchronization
- project scope / scope creep
- learning webdev (half of our team is new!)
Accomplishments that we're proud of
- a finished product!
- realtime functionality
- something that we would actually use ourselves.
What we learned
- How 2 webdev
- Concurrency models
- Effective state management
What's next for Clide
- Prettier, flashy interface
- Evil randomizer to randomly choose a presenter
- Uploading slides from Google Drive/Microsoft OneDrive
- Integration to Google Classroom
- Better audience reactions
Log in or sign up for Devpost to join the conversation.