Inspiration

As university students, we had our fair share of waking up feeling absolutely horrible. We're tired, annoyed by the alarm, dehydrated, and can't remember what our daily plans are. We need a solution that helps us get out of the right side of the bed every day. Upon further research, we found that the average human needs to drink 650ml of water when they wake up. Therefore, we decided to build an alarm clock that encourages the user to drink water when they wake up, as well as incorporating many quality-of-life improvements to the usual waking process.

What it does

The solution is an alarm clock that is can be turned off by the user drinking a sufficient amount of water. The user can download an app that allows them to customize the alarm tones, amount of water to drink, and alarm timings. The clock also links with the users Google Calendar and reads out the users daily tasks.

How we built it

The clockface is created using an OLED screen. A weight sensor is used to track the amount of water drank by the user in the morning. A speaker is used to play alarm tones. A Bluetooth module is responsible for sending information to and receiving triggers from the app. For the app, we used flutter to create an app that allows users to make their changes.
Created the app with Flutter.
Utilized Google Calendar API to fetch user's activities for the day. Used Google Text-to-Speech API to convert the users' activities into a .wav file in order to verbally announce their itinerary for the day.

Challenges we ran into

Integration was difficult for both hardware and software, as there were many components that needed to come together in a short period of time. Although the implementation is not complete, we have proven that our concept will work.
There was difficulty in creating the App as well as integrating the Google API's as it was our first time using Flutter.

Accomplishments that we're proud of

We're proud of learning how to use flutter to create an application that has many functionalities. Despite the many challenges we faced, we are glad to have pushed through and tried our best.

What we learned

We learned that we cannot code for 24 hours straight despite our most gung-ho attempts. In all seriousness, we learned a lot about the process of turning an idea into a tangible end product.

What's next for H2O'clock

Figuring out how to solve all our bugs and integrating hardware and software solutions together seamlessly.

Share this project:

Updates