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

React.ts, Emotion styled, Vite, Motion for little interactivity

emotion, framer-motion, pure-css, react, typescript
P
Dmytro•200
@DmytroVoitovych
A solution to the Frontend Quiz app 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 am most proud of successfully styling the range input in a way that not only looks visually appealing but also provides a clear and intuitive indication of progress toward the finish line. It’s a small detail, but one that significantly enhances the user experience.

Next time, I would take a more thoughtful approach to selecting the tools and structure for managing global state. I realized that some of my earlier decisions could have been better aligned with the complexity and scale of the project, and I want to ensure that future projects are built on a more solid foundation in this regard.

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

The biggest challenge I encountered was figuring out how to update the state of a parent component in response to an event triggered by a child component, especially since I wasn’t using context or a state management library. To overcome this, I decided to use a custom event as a signal, which could be intercepted by the parent component. This approach allowed me to establish communication between components without relying on additional dependencies, keeping the solution lightweight and efficient.

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

I would greatly appreciate any feedback on my project. Whether it's about the code structure, styling, or how I approached specific challenges, I’m open to suggestions and eager to learn how I can improve further.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Josh Kahlbaugh•540
    @Joshk7
    Posted 5 months ago

    This looks great! I really like the animations when the questions are answered. Also I like how your solution saves the user's progress. Honestly, I'd love if you'd explain how you did that with local storage because I've never implemented that in a project before. I really don't have much to say for what you could improve.

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