Full-stack Currency Converter

Solution retrospective
I'm most proud of the visual polish, the performance, the interactions and navigation for mobile devices, keyboard users, and screen readers. Next time I would do a couple things differently, such as refining and validating screen reader UX during initial component and feature development. I would also use grilling agents to craft detailed PRDs and TDD agents for implementation; I suspect this would improve E2E test suite coverage and reduce iterations.
What challenges did you encounter, and how did you overcome them?I chased a few goals: a pixel perfect visual layer, a perfect Lighthouse score, and thoughtful accessibility. Rendering as much UI as early and as smoothly as possible, took a lot of focus and effort.
Despite my best efforts, I couldn't manage a perfect Lighthouse score - Largest Contentful Paint was just 2 points shy of 100. The LCP elements - converter amount inputs - depended on URL state, preventing accurate and early rendering.
What specific areas of your project would you like help with?I welcome any feedback, in particular regarding performance and screen reader UX.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Bruno Cunha’s solution.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord