Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

Browser Extensions Manager UI with React, Zustand, and Framer Motion

react, tailwind-css, typescript, zustand, framer-motion
Sergejs•405
@Sergio0831
A solution to the Browser extension manager UI 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?

Most Proud Of:

I'm really proud of how smooth and fast the Zustand store implementation has turned out. It was my first time working with Zustand, and I managed to create an efficient, scalable store for managing the state of the extensions and their filters. The UI animations using Framer Motion are also something I’m particularly proud of — the transitions between active and inactive extensions make the app feel more polished and professional.

Another thing I’m proud of is the ability to dynamically toggle extensions and filter them based on their active or inactive state, providing a smooth user experience. The responsive design that adjusts to different screen sizes and the dark/light mode feature were also key components that came out well. What challenges did you encounter, and how did you overcome them?

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

What I Would Do Differently Next Time:

  • Modularize the store more: As the app grows, splitting the store into smaller, more manageable pieces might be beneficial. I’d like to see how splitting concerns between state slices (extensions, user preferences, themes) could improve performance.
  • Accessibility: While I’ve made efforts to improve accessibility, I think I could further enhance it by adding proper ARIA roles and testing accessibility across different screen readers and devices.
  • Better testing: I'd like to add more tests, particularly unit tests and integration tests for key components like FilterButtons, Extension, and state management to ensure reliability across updates.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sergejs'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
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.