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

React, TypeScript, Redux, Material UI & Tailwind CSS

material-ui, react, redux-toolkit, tailwind-css, typescript
Dima DB•40
@Bilostenko
A solution to the REST Countries API with color theme switcher 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 how everything came together — from a smooth light/dark theme toggle to responsive layout and efficient data fetching. Managing global state with Redux Toolkit made things scalable and clean, and combining Tailwind with Material UI gave me both flexibility and speed in building the UI.

If I were to do it again, I’d probably focus more on code splitting and lazy loading to further optimize performance. I’d also consider writing more unit tests from the start, especially for the search and filter logic — because even though "it works", future me will definitely appreciate having some safety nets in place 😅

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

One of the trickiest parts was handling edge cases when a user searched for a non-existent country. Initially, navigating back to the homepage after such a search didn’t work properly — especially when the user was stuck on a “no results” page. I fixed it by tweaking my routing logic and making sure the header click always redirects correctly using React Router's useNavigate.

Another challenge was balancing Tailwind with Material UI. Using both in one project can get messy fast, but I stuck to a rule: layout and spacing with Tailwind, components and accessibility with MUI. That combo kept things clean and maintainable.

I also had to wrangle with TypeScript a few times — especially when working with API responses. But once I defined solid types for the country data, everything became much smoother (and my IDE stopped yelling at me).

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

State Management — Am I using Redux Toolkit effectively, or is there a cleaner way to structure my slices/selectors/actions for a project of this scale?

Routing & Navigation UX — I had to manually handle some edge cases when navigating back to the homepage after searching for a non-existent country. Does the current solution make sense, or is there a more idiomatic way to handle this with React Router?

Component Structure — I aimed for reusable and scalable components. Would appreciate a second pair of eyes on whether my structure makes sense, or if I could decouple some logic further.

Styling with MUI + Tailwind — I’m mixing Material UI and Tailwind. Any tips on how to better balance or standardize the use of both, so it doesn’t feel like a tug of war?

Performance — Right now I fetch all countries on initial load. Is that fine for this dataset, or would you recommend a different strategy (pagination, caching, etc.)?

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 Dima DB'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.