Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Pomodoro App with React & Tailwind

react, tailwind-css, typescript, zustand
P
David Inoa•150
@davidinoa
A solution to the Pomodoro app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Difficulty in Implementing Custom Timer Logic

One of the main challenges I faced was implementing the custom timer logic for the Pomodoro, short break, and long break intervals. Specifically, ensuring that the timer transitions smoothly between different modes while updating the circular progress bar accurately. I'd appreciate feedback on how others have approached similar challenges and any tips for optimizing this part of the code.

State Management with Zustand

While Zustand provided a simpler alternative to other state management libraries, I'm curious to know if there are any specific best practices when using Zustand in a React project, especially when managing timers and user settings. Are there any common pitfalls or performance considerations I should be aware of?

Styling Consistency with Tailwind CSS

Tailwind CSS greatly facilitated the styling process, but I'm unsure if I've fully leveraged its utility-first approach. I want feedback on how I can improve the consistency and efficiency of my styling and whether there are any Tailwind CSS techniques or practices I might have overlooked.

I look forward to your insights, and thank you in advance for your valuable feedback!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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