Weather app

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

This project was an intentional revisit of core frontend concepts, particularly working with APIs and managing UI state effectively. While the application itself is relatively simple, I focused on keeping the implementation clean, predictable, and easy to maintain.

I’m most satisfied with how the data flow is handled—from fetching weather data to rendering it in a user-friendly way.

If I were to improve this further, I would focus on better separation of concerns, possibly introducing a more scalable structure for handling API logic and state. I would also refine the UI/UX with improved loading states and error handling for a more production-ready experience.

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

The main challenge was handling asynchronous data from the weather API while keeping the UI responsive and stable. Managing loading states and ensuring the app doesn’t break on invalid inputs required careful handling.

Another challenge was structuring the component logic in a way that remains simple but still scalable.

I addressed these by organizing state clearly, handling edge cases such as empty or invalid responses, and incrementally improving the UI feedback (loading/error states). Keeping the solution minimal helped avoid unnecessary complexity.