Build in Public

An architecture diagram can make every boundary look clean. Deployment reveals where the real boundaries are. With TimeSense, production work exposed issues that were easy to miss in isolation…

One of the most important corrections I made in TimeSense came from using the app on a real device. Calendar meetings were initially represented too much like tasks. That created contradictions…

I did not define Stage 1 of TimeSense as “a little bit of everything.” I defined it around one complete loop: Understand the day → calculate usable time → recommend what matters → learn from the…

TimeSense could easily have become another task manager. Projects, boards, labels, categories, drag-and-drop scheduling and complex routines all sound useful in isolation. Together, they would…

One of the first decisions I made with TimeSense was to build it as a true native mobile app rather than place a web application inside a mobile wrapper. I considered a cross-platform framework…