What it does.

An Android productivity app I built to fix a specific frustration: Google Tasks only surfaces recurring weekly tasks one day ahead. Focl handles tasks, events, habits, and weekly analytics — fully offline on my own device.

From prototype to a real debugging story.

• Started as a single-screen prototype, grew into a multi-screen app with persistence, search, and recurring-task regeneration.
• Hit a wall: the app built fine, but native features (back button, notifications, saving) silently did nothing — no error to google.
• Reasoned backward: if the build passes but native calls no-op, the plugins aren’t loading at runtime → traced it to module resolution in the Android WebView, and fixed the import strategy.

Diagnosis is reasoning over symptoms, not memorizing APIs.

I understand the logic of my code better than I know every library’s syntax — and this project showed me that’s enough to debug hard problems. I used AI to accelerate the build, but the diagnosis was mine. That’s exactly the gap I want to close: from directing the architecture to owning more of the implementation.