Inspiration

We were inspired by only applications that are already on the internet, and we looked at different Github repositories to find an application that was most similar to the idea that we wanted to use. We ended up using https://github.com/Cyberkid2311/Size-Estimator-and-Virtual-TryOn/tree/main as it was the most successful in providing the necessary code that we would need for our project, as well as explaining the code it was providing.

What it does

This application asks the user for their gender and the type of clothing they want to wear. Afterward, the user uploads a full body shot to the program to be analyzed and evaluated. Upon this evaluation, the code then pulls specific clothing items from Amazon and finds the best prices for the specified clothes.

How we built it

For the backend, we sourced information from the Github. We extracted the files by downloading them onto our computer, and using both Anacomeda and Git to extract the data. We used VisualCode to help build certain aspects of the code, and we also used Google Colab to create two helper functions.

For the frontend, we used VisualCode. More specifically, we used the Python import Tkinter to create the necessary GUI components that would be shown on the screen.

Challenges we ran into

Along the way, we ran into several challenges. Parts of the code that we were sourcing from the Github repository was out of date, making it hard to access certain file paths and other necessary components of the code used. We experienced challenges such as confusion, code not choosing to work, and applications not being able to download. Additionally, we wanted to use the CustomTkinter package but VisualStudio only knows Tkinter so we could not make custom GUI. We ran out of time, but we were planning to implement API's such as OpenAI's speech recognition, text to speech, and generative text APIs. Some of the challenges we experienced were new for us and it took us time to overcome these challenges.

Accomplishments that we're proud of

We are mainly proud of being able to overcome accomplishments and work together to get the job done. We were clear in communicating which members of the group had which roles, taking into account where people struggled with their roles and where people succeeded with their roles.

What we learned

We learned a lot of stuff regarding APIs and pull requests from outside sources.

What's next for Get Fitted

There are a lot of improvements that could be made to make Get Fitted better. First, we would want to find a way to get custom GUI into the front end instead of being limited by the generic Python GUI library. Then, we would add in the APIs that we omitted due to timing constraints.

If we decide that we want to continue on Get Fitted, we would do a few changes. First, we would

Built With

Share this project:

Updates