World’s Cutest Pomodoro Timer Is Also A Clock

Pomodoro timer helps you focus on tasks without burning out.

Student and hacker [prusteen] recently fell in love with the Pomodoro method of time management. That’s where you concentrate on your task for 25 minutes, then take a five-minute break, and repeat this four times with a longer break at the end. Initially, [prusteen] was keeping track on their phone, but hated having to change the timer value between Pomodoros and break times. In order to keep the flow mode engaged, [prusteen] came up with this darling little study buddy that does it all with the push of a button.

By default, this tomato shows the current time, which we think is a handy and often-overlooked feature of Pomodoro timer builds. Press that momentary switch on the front, and it starts counting upward to 25 minutes. Then it beeps in stereo through a pair of buzzers when the time is up, and automatically starts a five-minute break timer. Press it again and the display goes back to clock mode, although judging by the code, doing this will cancel the timer.

Inside the juicy enclosure is an Arduino Nano, an RTC, and a 7-segment display. We love the attention to detail here, from the little green leaves on top to the anatomically-correct dimple on the underside. And we always like to see lids that snap on with magnets. So satisfying. Check out the brief demo after the break, which unfortunately does not include any lid-snapping action.

Do you need more interaction with your Pomodoro timer? Build yourself a pomo-dachi instead.

17 thoughts on “World’s Cutest Pomodoro Timer Is Also A Clock

    1. I kind of agree, but against that I don’t want something that’s supposed to aid concentration to be busy and distracting. In fact, maybe it should have a gray-code display to minimise changes.

      1. @Kyle K said: “So what would you have people call things that tell time and dare to not care about seconds?”

        I would call them inaccurate and misleading. As a Human on Earth my temporal existence demands a minimum of seconds resolution and ±3.5ppm precision from -40°C to +85°C with at-least once daily updates from a Stratum-1 disciplined source.

  1. But (judging by the code), it does display seconds in timer mode, which is when you want to avoid distractions. Additionally/instead, I’d like to see some indication of where it is in the Pomodoro cycle (working, short break, or long break, plus how many pomodoros until the next long break), which could also (with the ability to set the position in the cycle using a long press or something) help you get it back to where it was in the cycle after you accidentally reset it. (Actually, with the current code, it looks like it just alternates between 25-minute and 5-minute periods, not supporting long breaks at all unless you implement them manually in how you use the device, so that would need to be fixed first.)

  2. Needs a contrast filter—I can barely read the display!

    (And my above comment was meant to be a reply to adrian godwin, but ended up at the top level, as sometimes happens.)

  3. Kristina Panos said: “Student and hacker [prusteen] recently fell in love with the Pomodoro method of time management.”

    Interesting; before now I knew nothing of the The Pomodoro Technique. A deeper dive – excerpting [1]:

    “The Pomodoro Technique is a time management method developed by Francesco Cirillo in the late 1980s.[2] It uses a timer to break work into intervals, traditionally 25 minutes in length, separated by short breaks. Each interval is known as a pomodoro, from the Italian word for ‘tomato’, after the tomato-shaped kitchen timer Cirillo used as a university student.[3]”

    * References:

    1. Pomodoro Technique

    https://en.wikipedia.org/wiki/Pomodoro_Technique

    2. Cirillo, Francesco. The Pomodoro Technique.

    https://francescocirillo.com/pages/pomodoro-technique

    3. A Pomodoro kitchen timer, after which the method is named.

    https://en.wikipedia.org/wiki/File:Il_pomodoro.jpg

    1. Really it’s just the automation idea that makes it worth writing up. The details can be found in the code, but anyone wanting to make one would likely use the parts they had to hand. Maybe a schematic would be helpful, but it would be silly to exclude the description for the lack of one.

Leave a Reply to tekkieneetCancel reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.