The latest articles on DEV Community by Nicolas Lens (@nicolaslens). https://dev.to/nicolaslens https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4030354%2Feaf2e2e7-59bd-4b14-8b76-f823b212da88.png https://dev.to/nicolaslens en Nicolas Lens Wed, 15 Jul 2026 11:58:36 +0000 https://dev.to/nicolaslens/i-built-roxima-focus-to-turn-a-project-backlog-into-a-three-task-focus-queue-2k0o https://dev.to/nicolaslens/i-built-roxima-focus-to-turn-a-project-backlog-into-a-three-task-focus-queue-2k0o <p>Most task managers are good at storing everything I <em>could</em> do. My problem started one step later: when I opened a project with twenty tasks, I still had to decide what to start, estimate a useful session, and resist reorganizing the list instead of working.</p> <p>I built <strong>Roxima Focus</strong> around a smaller execution loop.</p> <h2> The workflow </h2> <ol> <li>Keep tasks inside their real projects.</li> <li>Add no more than three tasks to <strong>Today</strong>.</li> <li>Keep the current task beside a Focus timer.</li> <li>Finish or mark it blocked.</li> <li>Move to the next task without reopening the whole backlog.</li> </ol> <p>The daily queue only references the original tasks, so completing one does not create a disconnected copy.</p> <h2> Why three priorities? </h2> <p>Showing a single task felt too rigid. Showing an unlimited list recreated the same overload I was trying to remove.</p> <p>Three is my current compromise: enough choice to adapt to energy or context, but small enough to make starting easier. The first task is highlighted, but the user can select either of the other two.</p> <h2> What I am testing now </h2> <p>A first session is not enough evidence that the workflow is useful. The product question is whether someone voluntarily returns on another day.</p> <p>I am therefore running a tiny public beta for freelancers and solo builders:</p> <ul> <li> <strong>Day 1:</strong> choose one real task and complete one Focus session of at least five minutes.</li> <li> <strong>Day 2:</strong> return and complete another session.</li> <li>Then tell me what helped or almost stopped the return.</li> </ul> <p>The app now offers an optional calendar reminder after Day 1. It is deliberately a normal calendar link rather than a push-notification system.</p> <h2> Implementation notes </h2> <p>The interface is built in vanilla JavaScript. Authenticated task and Focus history are synchronized with Supabase, while the public demo can be tried before creating an account.</p> <p>I am intentionally postponing automated AI prioritization. The manual loop needs to be understandable and useful first; later, an AI manager could call the same operations instead of creating a parallel workflow.</p> <p>You can try the public beta here:</p> <p><a href="https://roxima.io/?utm_source=devto&amp;utm_medium=community_post&amp;utm_campaign=devto_two_day_pilot" rel="noopener noreferrer">https://roxima.io/?utm_source=devto&amp;utm_medium=community_post&amp;utm_campaign=devto_two_day_pilot</a></p> <p>It is free, with no credit card and no sales call.</p> <p>Critical feedback is more useful than encouragement. I am especially interested in:</p> <ul> <li>Was the first action obvious?</li> <li>Did the three-task limit reduce hesitation or feel artificial?</li> <li>What nearly stopped you from returning on Day 2?</li> </ul> showdev productivity javascript webdev