Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Pomodoro Timer using Chakra UI

chakra-ui, next, react, framer-motion
Po-Cheng Yeh•190
@blp100
A solution to the Pomodoro app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I really appreciate the Pomodoro timer concept, and the appealing UI design is another reason why I chose this project. Additionally, I wanted to enhance my knowledge of CSS animation, making it the third reason take this challenge.

This is my second time use the Chakra UI, and I wanted to become more acquainted with framer-motion. That's why I built the "status bar" myself. However, I encountered several challenges with framer-motion, particularly because some instructions were not documented officially.

Luckily, I stumbled upon some amazing examples in the following link. If you're interested in framer-motion and want to delve deeper, this resource provides the best instructions available: https://blog.maximeheckel.com/posts/framer-motion-layout-animations/

For the next step, I made slight changes to the "Settings" page to ensure a consistent visual design throughout the entire interface. It was a lot of fun trying my hand at UI design. I drew inspiration from the concepts outlined in this article: https://www.halo-lab.com/blog/dark-ui-design-11-tips-for-dark-mode-design

And, the last challenge, is I was a little busy when I took this challenge. quite hard to concentrate on it. But still feel so satisfied when I finish this project. I look forward to making further improvements to this Pomodoro timer in the future.

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 Po-Cheng Yeh'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.