Mic Runner - cs428TAs/w2025 GitHub Wiki
- Status Report 1
- Status Report 2
- Status Report 3
- Status Report 4
- Status Report 5
- Status Report 6
- Status Report 7
- Status Report 8
- Status Report 9
- Status Report 10
Name | Role | Team(s) |
---|---|---|
Quenton Barger | Audio Designer | Participant |
Charles Johnson | Project Manager | Manager |
Molly Remer | Lead UI/UX Designer | Quality |
Parker Shumard | Chief Architect | Manager |
Daniel Spiesman | WebRTC/R&D | Presenter |
Brixtin Walker | Participant Lead | Participant |
Conner Wattles | Product Manager / Testing & QA | Quality |
Kaiden Williams | Presenter Lead | Presenter |
View Chart
View Requirements
Mic Runner will have four teams. The management team consists of the project manager and chief architect. The participant team is responsible for the web page for participants (i.e., audience members). They will handle both the audio input and web page. The quality team ensures UI/UX consistency across pages and general product quality. Furthermore, they will coordinate product design decisions to reflect real-world needs and/or wants, collecting feedback from real-world testers. The presenter team is responsible for the web page for presenters. They will coordinate the communication between the participant peer and the presenter peer, working closely with the participant team to define the communication interface. Both web page teams have a research member who will focus on issues that will likely be pertinent to the respective pages.
Project Manager (Charles):
- Final word on project deliverables
- Manage communication between Participant, Quality, and Presenter Teams
- Responsible for working with the CA to prioritize features and keep the project on schedule
- Ensures project deliverables are completed in a timely manner
Chief Architect (Parker):
- Final word on technical design decisions
- Responsible for creating coherent design across all features
- Communicates directly with each team and with the PM
UI/UX (Molly):
- Responsible for user interface and experience for participant and presenter views
- Makes design decisions regarding Model classes
- Coordinates with Presenter and Participant team leads to create a smooth user experience
- Final word on UI decisions
Product Manager (Conner):
- Responsible for product testing, deployment, and quality assurance
- Coordinates testing with Participant and Presenter Leads
- Provides real-world feedback to guide feature development, reports to PM and CA
Participant Lead (Brixtin):
- Responsible for the design and implementation of participant web page
- Coordinates with UI/UX lead to create a smooth user experience
- Coordinates with Product Manager to ensure quality
- Coordinates with Presenter Lead to ensure peer-to-peer communication flows between participants and the presenter
WebRTC/R&D (Daniel):
- Responsible for peer-to-peer communication between participants and the presenter
- Researches possible peer-to-peer technologies
- Responsible for the design and implementation of participant web page
Presenter Lead (Kaiden):
- Responsible for the design and implementation of presenter web page
- Coordinates with UI/UX lead to create a smooth user experience
- Coordinates with Product Manager to ensure quality
- Coordinates with Participant Lead to ensure peer-to-peer communication flows between participants and the presenter
Audio (Quenton):
- Responsible for participant audio
- Researches ways to avoid audio feedback
- Responsible for the design and implementation of presenter web page
Have you ever been in an audience where one or two microphones are passed around for questions? Imagine a solution that lets audience members use the microphone on their personal smartphone, with their voice broadcast directly over the rooms speakers. This would eliminate the need for "mic runners" or a single physical microphone being passed around. I'm imagining the audience could scan a qr code, or input a room pin and then tap to speak.
Features:
- Real-Time Audio Broadcasting: Audience members can use their smartphones as microphones, streaming their voice to the room's speakers in real-time.
- Feedback and echo cancellation: AEC (acoustic echo cancellation) implementation to ensure clear audio quality
- Push-to-talk: Mics only active when users press a button
- Moderator Controls: muting users, moderating when the audience can speak, queuing questions
- Local Wi-fi based architecture? bluetooth mesh network? for low latency
- WebRTC?
Proposed by Molly Remer