What Rymi won't do
Some of the most important decisions in Rymi are the features it does not have. These are deliberate, not a roadmap of things coming later. The constraints are what keep the app focused.
No time-blocking or calendar integration
Section titled “No time-blocking or calendar integration”Tasks are not calendar events. The daily ritual is the scheduling mechanism. If you need to know when something happens at a specific time, that belongs in a calendar. Rymi is for what, not when.
No subtasks
Section titled “No subtasks”Subtasks create depth that becomes clutter. If a task needs subtasks, it is probably a project. Projects group related work without hierarchy.
No team workspaces
Section titled “No team workspaces”Collaboration in Rymi happens through a shared project, not an organisational structure. Rymi is built for individuals and small, informal groups, not teams with roles and permissions.
No auto-prioritisation or AI scheduling
Section titled “No auto-prioritisation or AI scheduling”Rymi gives you information to decide; it does not decide for you. The daily ritual is where you prioritise. Every feature that automates a decision removes a chance to think clearly about what actually matters.
No energy or context tags
Section titled “No energy or context tags”Tags like “low energy” or “@errands” go stale the moment you create them. Rymi trusts you to make that judgment fresh each day while planning, rather than maintaining metadata that pretends to know your day in advance.
The thread through all of these is the same: the tool should support judgment, not replace it. If you have ever felt that a task app slowly turned into a second job, these constraints are the answer to that.