All solutions

What are you most proud of, and what would you do differently next time?

I liked building my own input components, as opposed to using libraries. Though, in a realistic scenario, I'd prefer a well maintained component library to ensure quality and accessibility right off the bat.

What challenges did you encounter, and how did you overcome them?

I needed to fetch again for each border country. It wasn't hard but I looked for options as to not overload the server with requests.

What specific areas of your project would you like help with?

Accessibility, probably. As stated in my README, I'm going to update this repository with accessibility features.

What are you most proud of, and what would you do differently next time?

I already have experience with APIs, so I used this challenge to test this platform and see how it works. To make the challenge more interesting for me, I added some extra features, such as a spinning animation to the button when it's clicked, a toast component that appears when the API is on cooldown to avoid it being mistaken by a front-end issue. I also added a toggle component that allows the user to disable the toast notifications. The user's choice is saved in the local storage, so it persists even after the user refreshes the page.

What challenges did you encounter, and how did you overcome them?

I always forget how to make the toggle work, so I have to check W3Schools every time.

What specific areas of your project would you like help with?

As of right now, none!