Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Timeboxing vs. Time Blocking #49

Open
latetedemelon opened this issue Mar 10, 2025 · 2 comments
Open

Feature Request: Timeboxing vs. Time Blocking #49

latetedemelon opened this issue Mar 10, 2025 · 2 comments

Comments

@latetedemelon
Copy link

Currently, your app schedules tasks using time blocking, meaning each task is assigned its own dedicated time slot. What if you implemented timeboxing instead? With timeboxing, you’d schedule a fixed period (say, one hour) during which you work on a group of related tasks that meet certain criteria.

For instance, consider designating one hour to handle various kitchen-related tasks. Within that hour, you’re free to tackle as many—or as few—tasks as you can manage. You might choose to wash dishes, clean the counter, or organize utensils. The number of tasks completed during that hour depends on the workflow and priorities, not on a pre-defined task duration.

In contrast, time blocking is task-specific. For example, if you know that cleaning the kitchen sink takes about 30 minutes, you’d schedule a 30‑minute block solely for that task—committing to one defined activity with an estimated duration.

Timeboxing offers the flexibility to work on multiple tasks within one fixed time “box,” making it especially useful when you have a set period available or are uncertain about the duration of individual tasks. On the other hand, time blocking allocates a specific amount of time to a single, clearly defined task.

Here is an example from Morgen.

Image

@vhsdream
Copy link

I second this. So far I haven't been using the Tasks function as much as I thought I would since I haven't been breaking down things into several different tasks. So if I've wanted to work on a task that overall might take several hours I'd like for some way to be able to break that up over several days/weeks until the due date.

@eibrahim
Copy link
Contributor

This is very cool... let me stabilize the app and work out all the kinks and will look into it. I think it would be very useful.

I have some performance issues with the auto-schedule algorithm which is high priority otherwise no one will use the app :)

FYI. The SAAS beta is almost ready and you can join at https://fluidcalendar.com/

My plans (at least for now) is to keep the open source in-sync with the saas version. I hate when apps limit the open source version to force you to upgrade, but we will see how things progress. I am sure at some point there will be a financial need, but i am hoping enough people will subscribe which will support the open source and saas - everyone wins :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants