Description and overview of our project and its features.
Uno, the smart assistant, helps you pick out an outfit perfect for the weather. While using a Google Home or an Alexa device, you can simply ask to “Talk to Uno”, and Uno will take it from there. Based on your location, your local weather, and your gender, Uno suggests clothes that will keep you comfortable all day long. With over 1.5 million combinations of responses, Uno can suggest outfits that contain anything from a formal suit to a casual sweater. With up to five days of forecasting, Uno considers wind speed, temperature, and precipitation for the most optimal outfit.
Why did we choose our project?
We chose this project because we wanted to push ourselves to do something different. In the past, we have worked a lot with mobile applications and databases. With HackUNO, we wanted to expand our horizons by creating a Google Action and Alexa Skill. We had not made such a thing before, so we thought we would give it a try. Typically, at past hackathons, we made applications with the goal of helping others. As a result, we wanted to continue this trend by creating Uno.
Difficulties we faced while completing the project.
What libraries, frameworks, and technologies did we use?
What's in store for the future of this project?
In the future we would like to increase the forecast rates, so users can plan their outfits farther in advance in case they are packing a vacation. We would also like to add more occasions such as weddings and vacations. More occasions give the users more flexibility in how they use our app. Another feature we would like to add is tailored outfits based on the clothes the user has. We would like for them to be able to enter the clothes they have and the app recommend them items from those.
What did each team member contribute?
Tommy: While on this project, I have worked on getting the longitude and latitude. These two systems would be passed to the AccuWeather API to get the forecast. I have also worked on setting entities and intents specifically on DialogFlow. The entities and intents are, in turn, used as different actions within our application. Aside from these two things, I also peer programmed with Danny and Emma on other tasks.
Danny: Throughout this project, I was able to work with our AccuWeather API calls and setting profiles for our users. With AccuWeather, I worked on getting the API calls to give, both, daily and a future five-day forecast. This would then be used to determine possible outfits that the user can wear. With profiles, we wanted the user to have the capability to set their preferences for temperatures. This would give the user more freedom and opportunity to wear more comfortable clothing.
Emma: During this project, I focused on writing the algorithm that determined what outfit to suggest to the user. I compiled lists of outfits to pull from, and I determined the default conditions for each type of outfit. The user can later change the default settings so that they can have a personal experience.
What did each team member learn?
Tommy: I have learned quite a bit throughout this project. I initially learned how to transfer a project from one framework to another without any overlaps. I had also learned how to make asynchronous functions for the first time. This concept is definitely applicable to many other software concepts. As a developer, I did not have much experience making logos. While working at HackUNO, I was able to create a great logo! Along with Google Actions, I believe that I did a better job of creating a conversation smoothly.