What I learned from building a planning system · Paused
CraigOS
I built a planning prototype because storing a task wasn’t enough. I wanted to trust that it would come back at a time when I could do something about it.
I’d tried different ways of planning, from task lists to calendars and Bullet Journaling. Each helped, but I kept coming back to the same question: where does this thing belong, and when will I see it again?
With Codex helping with the code, I worked on an iPhone app with places for tasks, projects, waiting items and planned time. My part was defining the rules, trying the app in daily life and noticing where the experience didn’t match the intention.
Testing exposed a bigger problem than the layout. Different screens could give competing answers about where work belonged. I preserved the prototype and reconsidered the foundation. CraigOS is paused now; the screenshots document that work, rather than a finished product I use every day.
What I take from it
A convincing interface can arrive before a system deserves your trust. Living with the prototype taught me what still needed to work.
A closer look
