Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 22 days ago

Responsive product list with cart using reactjs and typescript

react, react-router, tailwind-css, typescript, zustand
Amiko Elvis•260
@amikoelvis
A solution to the Product list with cart challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I'm most proud of the seamless interactivity of the product selection and cart system especially the way items update in real time with visual feedback (like the orange border, quantity controls, and cart breakdown). Implementing this with Zustand and React while keeping accessibility in mind was both fun and challenging.

If I were to do this again, I'd focus earlier on accessibility and responsiveness to save time later in the project. I’d also aim to implement unit tests from the beginning and possibly use a design system or component library to scale styling more efficiently.

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

One of the biggest challenges was managing dynamic cart state—ensuring accurate updates when users added, removed, or adjusted item quantities. It was especially tricky to sync UI changes with underlying state logic while keeping the interface responsive and intuitive.

I overcame this by refactoring the cart logic into a centralized Zustand store. This allowed for consistent state updates and simplified data flow across components. I also used conditional rendering and Tailwind utility classes to provide real-time visual feedback (like changing the button layout and highlighting selected products), which helped reinforce the state changes for users.

Styling the modal to be centered, non-stretching, and with a proper dimmed background was another challenge. I experimented with different layout and backdrop-blur strategies until I found a clean, responsive solution that worked well on all devices.

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

I would appreciate feedback on improving the overall structure and maintainability of my state management setup. While Zustand worked well for this project, I’m curious if there are best practices I might have missed—particularly for organizing more complex state logic like modal handling, cart quantity updates, and product caching.

Additionally, any insights into optimizing performance (e.g., reducing unnecessary re-renders or enhancing accessibility) would be valuable. I tried to implement good UI/UX practices such as keyboard navigation and proper focus management, but I’d love a deeper review to ensure it meets accessibility standards.

Finally, I'd welcome suggestions on code organization for larger projects—especially how to keep components clean, modular, and scalable as functionality increases.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • OlgaMinaieva•80
    @OlgaMinaievaWebDev
    Posted 20 days ago

    good job. i wish i knew Zustand

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub