/breaktimer-app

Manage periodic breaks. Avoid eye-strain and RSI.

Primary LanguageTypeScriptGNU General Public License v3.0GPL-3.0

BreakTimer App - https://breaktimer.app

🔨 Looking for contributors 🔨 If you feel like getting involved, please get in contact!

BreakTimer is a desktop application for managing and enforcing periodic breaks. BreakTimer is available for Windows, macOS and Linux.

BreakTimer allows you to customize:

  • How long your breaks are and how often you wish to have them
  • Whether to be reminded with a simple notification or a fullscreen break window
  • Working hours so you are only reminded when you want to be
  • The content of messages shown during breaks.
  • Whether to intelligently restart your break countdown when it detects that you have not been using the computer

Installation

Screenshots

break panel

settings panel

notification

FAQ

Why can't I see the app in the tray?

Some operating systems, such as linux distributions running plain Gnome (e.g. Fedora) or Pantheon (e.g. Elementary OS), don't support system tray icons. In this case, simply re-run the app to open the settings window. You will lose access to certain functionality only available in the tray menu, but at least this workaround lets you use the app.

Is there a way to control the app via the commmand line?

On linux, if you run the app via the command line there is some basic support for command line arguments:

Disable breaks:

breaktimer disable

Enable breaks:

breaktimer enable

How can I pass you my log files to help you debug an issue?

You can find the log file for BreakTimer here:

Linux: /home/<USERNAME>/.config/BreakTimer/log.log

macOS: /Users/<USERNAME>/Library/Logs/BreakTimer/log.log

Windows: C:\Users\<USERNAME>\AppData\Roaming\BreakTimer\log.log

You can either upload this to a cloud service such as Dropbox or Google Drive and enable public sharing, or you can email the file as an attachment to contact@breaktimer.app. The log files do not contain any personally-indentifying information.

Please try and include a timestamp for roughly when you have seen the issue so that I can find the relevant place in the log file.

Development

See ./DEVELOPMENT.md.