Household chores, availability, and scheduling, connected so that the next task reflects what has actually happened.
Actual task editor captured from the application development preview. The steps are empty demo inputs. This later screen separates a transition delay from the repeat interval of the sequence.
The project
Shared routines, built around real life.
A recurring reminder cannot tell the whole story of a shared home. People leave, come back, complete a chore early, or do the first step of a task that someone else needs to finish. WGTakt connects those events to the schedule.
This project spans mobile interactions and backend rules. Painting availability should feel immediate. A monthly task should use a calendar month. A linked task needs an event and a delay, not just another item in a list.
The journal shows how I use detailed development conversations, prototypes, implementation checks, and real use to work through those decisions. Household identities and private activity are left out of the public account.
01
Capture the useful context
Broad availability, time away, and quiet hours should take less effort than maintaining another personal calendar.
02
Let events drive the schedule
Completion, rescue, and linked tasks change what should happen next. Fixed and completion based schedules need different rules.
03
Design for a group
Joining a household, sharing future turns, and seeing the consequences of an edit all need to work beyond the single user happy path.
Original captures, visible details, and room to look closer.
Screen capture · 27 Jul 2026Painting a typical weekA later onboarding capture showing broad availability states and the weekly grid. This July screen illustrates the continuing evolution after the May paint week change.Screen capture · 31 May 2026A chain begins with a real taskThe original linked chain builder capture: define the first task, its start, and its completion based cadence.Screen capture · 31 May 2026What makes the next task start?The follow up task has its own area, effort, and trigger. The original capture also shows the cramped boundary near the delay field; this is implementation evidence, not a polished recreation.Screen capture · 7 Sept 2026A range selected directly on the calendarActual Android application capture from the development checks. Two selected dates, From and Until summaries, and collapsed time controls are visible. This is later evidence of the July interaction.Screen capture · 8 Sept 2026Chat with the full navigation in viewActual application development capture with synthetic QA household messages. It shows the reading state. Keyboard transitions and native safe area behaviour require separate device checks.
