The document describes an app called Sleep Buddy that was created to help hackathon organizers broadcast information to attendees and provide a centralized resource for hackers. The app allows organizers to send push notifications and dynamically update schedules, while hackers can stay up-to-date on events, contact mentors, and find locations on maps. Feedback from users praised its ability to seamlessly connect sponsors and hackers while creating a living schedule. The creators aim to test the app at multiple events in the coming months to refine it before adding additional features like awards and registration.

1. Hackathon App
Sleep Buddy Team:
Jeff Hurray, Dylan Hurd, Tom Erdmann, Sylvie Zhang
sleep-buddy@umich.edu

2. Problem
● Hackathons organizers have trouble broadcasting information
● Existing solutions have different and incomplete feature sets
● Lack of uniform platform across hackathons

3. MVP 2.0 Improvements
● Push Notifications
○ Generated by organizers
● Contacts Redesign
○ Better communication UX
● Login/Signup Flow
○ Better error messages on failure
● Maps
○ Locations for events

4. Use Case
● Hacker
○ Centralized hackathon resource
○ Stay up-to-date on important information
○ Contact mentors
○ Locate certain venues for events
● Organizer
○ Quickly broadcast important information in real-time
○ Dynamically update schedule

5. User Quotes
“The hackathons app not only connects sponsors with
hackers seamlessly, but creates a living schedule that
will allow hackers to take greater advantage of the
countless opportunities available at hackathons of any
size”
- Vikram Rajagopalan, MHacks Director

6. User Quotes
“As a hackathon organizer, I am always looking for ways
to communicate more effectively with hackathon
attendees. This app provides a way to cleanly present
critical logistical information without having to send an
unnecessary number of emails.”
- Katie Seigel, HackMIT Director

7. Lessons learnt
● Early, thorough research on abilities of technical platforms (Rails vs Node)
● Get builds in the hands of users early for customer identification and
usability testing
● Update quickly and frequently
● Stick to Agile development strategy

8. Moving Forward
● Testing at several events throughout January and February
● Testing, testing, testing
● Add awards and registration