All solutions

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

I'm most proud of the pixel-perfect results I achieved on this project. Next time, I would avoid spending too much time looking for new ways to handle font sizing on different devices. Since I'm using TailwindCSS, I can easily manage responsive designs with their built-in utilities, like sm:, md:, and lg: breakpoints, which simplify handling layouts for different screen sizes.

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

I focused on making the font responsive for each view without using media queries, as a personal challenge inspired by FrontEndMentor. However, as I mentioned earlier, since I was already using TailwindCSS, I could have easily handled the responsiveness with its utilities, making the process much simpler.

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

Honestly, I'm not sure what I would change in this project. If you have any feedback on areas I can improve or refactor, I would greatly appreciate it. Perhaps I could make the component more dynamic, but that wasn't the main goal of this project.

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

I'm proud of my pixel-perfect solution thanks to your Figma design. It was very easy to tackle this challenge with all the tools provided.

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

I think it wasn't a big challenge for me since I have a few years of experience. But I want to take the path of complete learning, you never know when you will find new techniques to solve a problem.

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

I don't know if the html tags I used are the most accurate for this challenge.

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

I am proud of the final result of the design.

I always start with the mobile part (mobile first always), but this time I started with the desktop part and it was a bad decision. It took me twice as long to make the changes so that the mobile part looked good without breaking the desktop design.

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

Saving the results of each step and being able to modify them I think was the most difficult part. More than anything because I used Redux and I haven't mastered it yet. But, the positive thing is that once you have redux configured in your project, it is very easy to use it or make changes.

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

I didn't do any testing. I would like to add some test cases for each step in case I make a future modification to the application and everything still works correctly.

I'd like to know if there are better ways to implement custom themes with TailwindCSS. It was a little difficult for me to solve this problem, but I managed it after all.

I also think the Calculator component is a bit complicated, but I couldn't do it better with React. I had some issues with the useState hook and its current value for operations.