What we're thinking about.
Posts about privacy, weekly planning, ADHD-friendly design, and building cross-platform with Expo. No newsletter signup, no popups.
-
Why sync stopped at 1,000 tasks
For accounts past 1,000 tasks, every change in weekkii synced and then reverted moments later. The culprit was a silent 1,000-row cap in our API layer.
-
The rollover that raised the dead
On June 11 a user watched tasks they had completed come back unchecked. A postmortem on a midnight rollover that raced our sync pull and won.
-
A list is a tag that sticks
We shipped named lists for undated tasks this June. Under the hood there is no list at all, and that was deliberate.
-
What we refuse to build
Our feature list is also a refusal list: no analytics, no third-party JavaScript, no server-side AI. Saying no is how a privacy promise stays true.
-
Offline is the default, not a mode
Every read in weekkii hits local SQLite and sync is background reconciliation. Here is what that architecture costs, and why we pay it.
-
Six digits, no password
Why weekkii sign-in is email plus a one-time code. Every credential we refuse to hold is a liability we cannot leak.
-
Your week, yours alone: what zero-knowledge actually means
When weekkii says we can't read your tasks, we mean it literally. Here's the architecture, and what it costs us.
-
The week is the unit, not the day
Most planner apps default to a daily list because it's simpler to ship. Weekly planning is harder to build, easier to live with.
-
Built for ADHD brains, by people who needed it
Time-blindness, task-initiation paralysis, decision fatigue: three reasons we built weekkii the way we did.