## Inspiration

We created Climately to change how people plan their days. Imagine being able to see real-time weather information right next to your schedule! By combining these features, we want to boost productivity and help users make better daily decisions, no matter the weather.

The best part? There’s no need to switch to an entirely new calendar; it effortlessly integrates as an extension of Google Calendar, one of the most popular calendars available, enhancing your experience without any hassle.

## What it does

Easily see your events with real-time weather updates and personalized scheduling suggestions. This helps you plan outdoor activities better and stay prepared for any weather surprises.

## How we built it

Our Chrome extension delivers real-time weather updates directly to your browser, offering quick, accurate forecasts and alerts without the need for external websites.

We chose React for the front end because it makes development easier and helps us create a dynamic user experience. Now, for authentication, we use Google OAuth, allowing users to send their Google Calendar schedules and preferences to the backend, which they can easily adjust in the extension.

Our technology stack is designed to create a seamless user experience, with Java Spring Boot powering the backend. We handle multiple APIs to ensure smooth integration, allowing weather-related events to be directly added to your calendar. We dynamically update these events using the Weather API and Google Calendar API. We utilize the OpenAI API for intelligent AI suggestions, evaluating whether to offer recommendations based on weather conditions and user event context, and providing options like rescheduling or alternative plans.

We’re hosting our backend on Digital Ocean, and we have exciting plans to launch our Chrome extension on the Chrome Web Store (currently under review), making it accessible to everyone!

## Challenges we ran into

We encountered challenges with Google authentication and sending data to the backend from our extension, which involved navigating some complexities. Since this was our first time building a Google Chrome extension, we also had difficulties with data storage on local devices because of permission restrictions.

On the backend, we encountered issues with intricate network processes that frequently caused our API calls to crash. We worked hard to fix these problems, which improved our application's stability and performance.

Despite these challenges, we persevered and built a product we are proud of.

## Accomplishments that we're proud of

We take great pride in our innovative idea, which modernizes calendar applications that have long needed an update. The seamless integration with Google Calendar ensures ease of use, eliminating the need for users to switch to a different platform.

We are also proud of overcoming the numerous challenges we encountered throughout development, particularly in combining multiple APIs and synchronizing the frontend with the backend—a task that is no simple feat.

## What we learned

Working with the OpenAI API and Google authentication taught us how to integrate advanced features into our app, significantly enhancing its functionality and user experience. Additionally, we navigated the exciting challenge of building and deploying browser extensions, which was a new venture for us.

We encountered several issues with HTTP server ports, but we’re proud to say that troubleshooting these problems deepened our understanding of how they operate. Our mentors played a crucial role during this process, guiding us through various challenges and helping us maintain composure while resolving issues. Their support not only improved our problem-solving skills but also made our development journey more enjoyable.

Many hurdles had to be overcome to orchestrate the front-end, Calendar, Weather, and Open AI APIs to provide a seamless and reliable experience. Effective use of documentation, Hackathon resources (mentors, workshops), and effective use of AI dev tools were key to the successful completion of the project.

## What's next for Climately?

We’re thrilled to announce our upcoming launch on the Chrome Web Store, making the Climately App accessible to a wider audience! We're also focused on introducing new exciting customizable preferences that empower users to personalize notifications and weather insights to fit their unique lifestyles!
## Inspiration

Even though the pandemic has been going on for a while, we found that a lot of people still had trouble dedicating time to spend with friends. Now that things are opening up again, we were inspired to create an app that can help with that.

## What it does

Our program finds free time in the user's calendar and using those free time slots creates a new calendar with recommendations on how to use the free time.

## How we built it

We used Google's oauth to create credentials for the app which we used along with Google's python API and oauth API to request user authourization and then access and interact with their calendar.

## Challenges we ran into

One of the challenges we had was with encryption. we did not know how to encrypt and decrypt our credentials so we had to leave it as is. Another problem we faced was setting contraints so that new events are not created during nighttime. Initially we set nighttime hours of 10 pm to 8 am, and we had some trouble in working around those constraints, but we eventually understood that it would be easier to hardcode those 15 minute blocks as busy, instead of trying to filter out the times when we created the events.

## Accomplishments that we're proud of

We're really proud of using this hackathon as an opportunity to expand our skills and try something new. All of us gained some experience with the Google Calendar API, which was completely new to us before this weekend. It was also really rewarding to actually get a working prototype that is relatively close to what we were imagining when we started the hackathon.

## What we learned

We gained a lot of experience through this hackathon. First and foremost, we gained experience using the Google Calendar API, creating a Google Cloud project to complete our task. In the process of finding free time in our user's schedule, we learned how to retrieve and read information about existing events. Then in creating events, we learned how to assemble a Json object that matched what the Google Calendar API was looking for in Python. We also learned about the authentication process in using the API, and understood ways to reduce the hassle of authenticating on each login. Moreover, in creating our application, we gained experience in thorpy, a GUI library that built upon pygame.

## What's next for Amitee

For Amitee, there's a lot of further development available to improve the functionality and flexibility in creating social opportunities for our users. The biggest change would be to improve our communication on our user interface of what our product actually does, adding events that represent possible ideas of how to constructively spend their free time. Moreover, we could add flexibility of which idea they want to do by providing the times they are free and a list of possible ideas for them to choose, instead of us randomly choosing one based on the length of free time. We could also provide more functionality on creating the calendar events, providing them space to type in descriptions and invite friends via email directly on our application, instead of having to coordinate with them separately.
## Inspiration

Time doesn't wait -- it moves regardless whether we are ready. Realizing that as college students, we've probably spent more than 90% of the time we will ever spent with our parents already, that we only have so many more winters, and that we should live consciously and reflect often -- not letting the time meaninglessly pass us by. We came up with an app that gives us context to the years gone by and the years to come in our lives.

## What Lifely does

1) Visualizes the user's age on a chart relative to a long human life

2) Provides contextual visualizations of a typical American life and also average age for other events, such as getting married or starting a successful startup

3) Insights on years past, such as: how old they were in a particular year, what significant events happened in that year (pulled using the WolframAlpha API), and how much an investment they made that year could be worth today.

## How we built it

Rapid ideation burning through a bunch of ideas, user testing to a pivot, learning a new tech stack we never used before, and lots of food.

## Challenges we ran into

The app started as a very depressing venture, both on the insights it gave and our progress. We spent 16 hours trying to build an MVP, and realized its only working functionality was something any three year old could have done -- count. We also decided to try Angular with no experience, and spent 4 man hours debugging a one-character error.

## Accomplishments that we're proud of

First Hackathon experience -- **We did it!** \_ (not sure how) \_

## What we learned

Coding is hard. CSS positioning is painful. Learn Angular ahead of time.

## What's next for Lifely

We would like to expand our MVP to include key functionality such as:

1) **Personalization** -- Give users the ability to integrate with Facebook and connect their Moments onto their Lifely Life Calendar, add their own notable events, and potentially save and share their calendars

2) **Business Development Opportunities** -- We would like to expand Lifely Insights to better connect users to products or services that solve their problems, such as investing platforms, health advice, career guidance, and going back to school

3) **Data Visualization** -- Our core value is around building context for the user with data, and we want to continue to develop the way we present our visualizations to be more relevant and impactful to our users such as by adding a weekly or monthly view