[Feature Request] Adding a Flow-State Mode in App

[Cloufish]

The Flow-State Mode would allow to:

1. Take breaks not when the timer runs out, but when we really need a break.
   • Oftentimes, the first Pomodoro session can be even 40 minutes long without taking breaks and you still do not feel like taking a break.
   • On the other hand, after a few Pomodoro sessions you might even be tired after 14 minutes of work
2. Not distracting yourself from being in the 'zone state'
   • Zone State - is referring to the moment when everything other than what you're doing ceases to exist
   • Being interrupted from this state might be frustrating, but a mindful user might decide for themselves when to stop the timer

The workflow in this would look like that:

1. the timer would simply count time,
2. After the user clicked on the timer BREAK would start up (this break could be calculated by TOTAL_MINUTES/4) or divided by the number 5.
3. When the BREAK ends, the WORK timer starts again.

The toggle settings to enable this Flow-State Mode might be on the general settings tab so that it doesn't interfere with the minimalistic interface

This option is provided by other competitive apps like ~Forest App~ <- I'm trying to not sponsor/advertise anything!!! :pray: I personally think this option would be even better in Goodtime App!!!

I don't have great mobile development experience, but I would really want to help out!

[adrcotfas]

Another user mentioned this: https://www.lesswrong.com/posts/RWu8eZqbwgB9zaerh/third-time-a-better-way-to-work I plan to add something like this in the next major release so stay tuned!

[yephny]

If you ever doubt if if it's really worth it along the way, I'd say it easily beats Pomodoro by a mile. I'll be looking forward to the next major release.

[Truncated]

As someone who hyper-focuses and relies on that state for specific types of work, it would be awesome if we could identify the sessions at the start, maybe by expanding tags to be different categories of tags?

I see the value and programattic benefit of maintaining one tag per session. Giving the tags a type between "regular" and "flow state" may be a clean way of implementing the flow state rules dynamically.

I'm also finding myself wanting to easily see the "job related thing" vs "personal" things... not sure how these ideas would best be reconciled to suggest a feature or something for that...

[adrcotfas]

What do you think about combining the current labels and time profiles to create a work profile that contains the following?

• type (countdown/timebox/pomodoro vs flow/count-up with work/break ratio)
• name
• color

This idea was mentioned here too: https://github.com/adrcotfas/Goodtime/issues/304