Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Pomodoro Timer | React | Redux | Styled Components | Sound Effects

Jen•1,230
@En-Jen
A solution to the Pomodoro app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey FM community! I don't have any specific questions but I'd love any/all feedback on this solution. I've only been learning React the last few months so any feedback on anything related to React, Redux, or Styled Components would be much appreciated.

I wasn't able to figure out how to style the arrows that the user clicks to increase or decrease the value in the inputs of type="number" in a way that it would work on all browsers so I just scrapped styling the arrows but I think that's something I can live with.

If you're curious to read more about this project, feel free to read the detailed README. Just to summarize, this project includes sound effects, Redux Toolkit for state management, and a few little animations 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aaron Stroud•435
    @astroud
    Posted almost 4 years ago

    Nice job Jen. There are so many ways to solve this project. I'll be looking over your code to see how you used Redux. I think it would have solved me a lot of trouble with my solution.

    I don't recall how I styled the input arrows, but I do remember them giving me a lot of trouble. I just checked them again in Chrome/Firefox/Safari and there's still some room for improvement.

    For my sound effects, I used Garageband and Audio Hijack to record the sfx I was considering. It's tricky finding the right notes/instruments but the audio quality is excellent.

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, Jen! 👋

    Congrats on finishing another challenge! I feel like you thought about everything in this project. I really like the animations, modal settings, sounds effects.. Great job! I found that arrows in number inputs aren't clickable. It is a little contrary to user intuition.

    Good luck with that, have fun coding! 💪

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hey, En-Jen! 👋

    Oh my goodness—your solution is amazing! 🤩 The animations and sound effects that you added fit the feel of the app perfectly! 👏 Everything works really well and you've definitely got my bookmark on this one! 😀

    The only very minor thing that I noticed is that the number in the timer gets rather close to the edges of the circle at certain screen sizes—you might want to bump down the font-size just a bit, then. 😉

    Keep coding (and happy coding, too)! 😁

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub