One long table. Something to share. Come over?
SAT17OCT
AN INVITATION FROM NEXT DOORCourtyard
Hofgarten courtyard · 18:30
Courtyard
dinner.
Hofgarten courtyard · 18:308 goingBring one dishFree to join
A place at the table is waiting.
← Back to my workWGTakt / PRODUCT, DESIGN & DEVELOPMENT
A little less household admin.
Less managing.
More living.
I’m building WGTakt for everything that happens between people who share a home. The chores. The changing plans. The people just around the corner.
Come insideYOUR SHARED HOMELinden 14
MLAN
WED, 14 OCT4 people · one home
Hey Maya.
Home is in rhythm.
3open home turns
4people at home
0done by you
The household planSee the plan ↗
Run the dishwasherLinked to Leo’s next turnLinkedWater the plantsWho is here mattersNShared shopping3 items
Oat milk · Tomatoes · Coffee
One list for everyone at home.One action. The next person knows.
01
Try ticking the floor chore.
The next date moves with it.
A HOME THAT KEEPS UP
I started with the chores. I ended up designing the connections.
SCROLL TO FOLLOW. TAP TO CHANGE.01 / 03
YOUR SHARED HOMELinden 14
MLAN
WED, 14 OCT4 people · one home
Hey Maya.
Home is in rhythm.
3open home turns
4people at home
0done by you
The household planSee the plan ↗
Run the dishwasherLinked to Leo’s next turnLinkedWater the plantsWho is here mattersNShared shopping3 items
Oat milk · Tomatoes · Coffee
One list for everyone at home.THE HOUSEHOLD PLAN3 open turnsOne useful glance.
01 / A SHARED HOME
Everything small.
Finally together.
I wanted opening the app to answer a simple question: what needs me today?
My turn, the next person’s turn, the shopping list and the people at home belong in the same picture. I designed an overview that connects them without making someone the household manager.
YOUR SHARED HOMETap a chore to try it
YOUR SHARED HOME
4 peopleLinden 14
Hey Maya.3 open turns · one shared plan
MRun the dishwasherMaya runs it. Leo empties it.NPlan around time awaySee who can take the next turn.
Tap the floor chore. See the next date move.
Follow the rolling rhythmYour turn. Their turn. The whole home in one view.
ChoresKnow your turn.ShoppingShare one list.PeoplePlan around real life.
Now let the plan move ↓02 / ROLLING CHORES
Every three days.
From the real day.
A clean floor does not know it is Thursday. I wanted the schedule to follow when someone actually cleans it.
Finish on Monday and it is due on Thursday. Finish that turn on Wednesday instead, and the next due day becomes Saturday. The following turn moves one day earlier too.
TRY THE RHYTHMFinish a day early ↓
ROLLING CHORE
Every 3 daysClean the floor
LAST DONEMon 12Maya
+ 3 daysDUE NOWThu 15Maya · 18:00
M12✓
T13
W14
T15Due
F16
S17
S18
The following turn is expected Sunday. Finish Thursday’s turn on Wednesday to move it.
Next, hand it to someone elseMonday + 3 days = Thursday. Tap Finish to see the plan move.
LAST DONEMon 12
+ 3 daysNEXT DUEThu 15 Oct
I keep the chosen deadline time. Rolling changes the due day; it does not force the person to finish at the same hour.
03 / LINKED CHORES
A chore can carry
the next person.
The dishwasher was my turning point. Running it and emptying it are two jobs inside one agreement.
I linked them through an action. Maya marks Run done. Leo’s Empty is confirmed for two hours later. Start early or late and the handoff moves with it.
TRY THE HANDOFFTwo people. Two steps.
LINKED CHORES
1 / 3One dishwasher. Two turns.
1 Run2 Empty3 Next cycle
M
Maya runs itReady to finish · 17:00
Your turnCompletion + 2 hours
L
Leo empties itEstimated · 19:00
WaitingStart with Maya. Her completion confirms Leo’s time.
Finish at
Next, someone goes away Leo sees an estimate. Maya’s actual completion sets his time.
Run at 17:00Empty is expected
↺
The last step starts the next rhythm. In this three day example loop, finishing Empty on Wednesday schedules the next Run for Saturday at the finishing time. Try completing that final step a day earlier too.
Where this decision started 31 May 2026
when you are building linked chains, it should ask both the tasks and if there are 3 task ability to add third and then condition on how they are linked, meaning after they are triggered, how much time the other task run after.
I had to describe the relationship, the trigger and the wait. AI helped me build it. The product decision was mine to make.
Plans change.A little rhythm for real life.
04 / LIFE HAPPENS
The home carries on.
Even when someone goes away.
I do not want a holiday to turn into a negotiation over every chore. Time away belongs in the plan.
I made availability part of who can take a new turn. Here, I’m planning a separate recycling chore for Saturday. Maya can choose two dates, and work can find someone who will actually be home.
Maya’s time away
Plan17 → 21 OctChange dates ⌄
October 2026Tap the first day, then the last.
New recycling turn · Sat 17 Oct
Mayais available
4 of 4 homeEvery 3 days
Existing open turn: Maya keeps it. No rescue request yet.
The little things between choresMAYA’S AVAILABILITYTime away
MLAN
A little time out.
October 2026MTWTFSS
Two dates. One clear plan.17 → 21 October
THE HOME’S SIDE OF THE STORY
MLAN
Four people.
One shared rhythm.
MMayaHome
LLeoHome
AAlexHome
NNoorHome
Recycling turn · Sat 17 OctoberMayaMaya is available for this date.
Recycling interval3 days
4 of 4 homeRegular rhythm
For the turn on 17 October. With three people home, the three day rhythm stays. With two, this chore’s enabled low presence setting stretches it to six days, within the two times cap.
01
Before the holiday starts.
Add Maya’s holiday to see how eligibility changes before an absence begins.
ALL THE LITTLE THINGS BETWEEN
A home is more
than a chore list.
I brought shopping, shared expenses, conversations and plans into the same place. The point is to spend less time coordinating life and more time actually sharing it.
THE SAME HOUSEHOLDOur shopping list
MLAN
On my way home.
Everyone can add. Anyone can pick it up.
1 of 3 picked up. One shared list.
05 / THE NEIGHBOURHOOD
A home is only
the beginning.
I wanted the people next door to feel a little closer. So I built a community around the home, with household profiles, open rooms, shared plans and a way to say hello.
The same neighbourhood, on the web and in your pocket.
FROM FLATMATES TO FAMILIAR FACES
THE NEIGHBOURHOOD FEED
Community
Linden 14 · within 1 km
€480/ monthWarm rent
A room. A little more life.
18 m² · From 1 November · Unfurnished
Shared dinnersPlants welcomeMEET YOUR NEIGHBOURS
Parkside WG
Three people. Shared dinners. A very full windowsill.
01 / THE WEBFind the people around your home.
Hofgarten WG
Nina · Event hostTODAY
Courtyard dinnerSat 17 Oct · 18:30
EVENTTap a message to keep the reply in context.
Prepared conversation · stays on this page
02 / THE NATIVE APPTake the conversation with you.
I connect the feed to events. A dinner has a host, a place and a response, so an invitation can become an actual plan.
Illustrative interfaces · fictional people
06 / BUILD, BREAK, REPEAT
The useful bugs
are the human ones.
I tested a complete move in. One household. Four accounts. One invitation. The first run was not frictionless.
People could join, but the app needed a restart and the creator still held every chore. I had to fix the journey and the plan behind it.
My rule became simple: share unopened future fixed chores when someone joins. Keep work that is already open, overdue or complete with its person.
Maya
7 chores- Fresh towelsCurrent · stays
- Shared laundryCurrent · stays
- Kitchen resetFuture
- Hallway floorFuture
- Bathroom resetFuture
- Take out the binsFuture
- Water the plantsFuture
Leo
0 choresJoined the home. No turns yet.
Alex
0 choresJoined the home. No turns yet.
Noor
0 choresJoined the home. No turns yet.
Four people joined. Maya still had all seven chores. Testing the whole journey exposed a gap that a successful invite alone could not show.
Current turn stays Unopened future turn can movePrepared example · fictional roommates
01
The whole move in
I tested four accounts and one reusable invitation. The first run exposed the join route, names and app refresh.
July 2026 · recorded test02
A plan that stays fair
I checked that joining changes unopened future fixed work while keeping current, overdue and completed turns stable.
July 2026 · recorded fix03
One event, one handoff
I traced duplicate prevention, durable notification retries and quiet hours in the existing linked task tests.
Current code · source reviewed04
The UI under pressure
I checked English and German, both themes, narrow screens and larger text. Wrapping failures were fixed and checked again.
8 October · recorded checksONE PRODUCT, CONNECTEDI built across the interface
I built across the interface
and the rules underneath.
Native household screens in Expo. A neighbourhood on the Next.js web app. A shared TypeScript and PostgreSQL backend that owns the scheduling.
8 OCTOBER · RECORDED MOBILE SUITE3,472passing tests in the saved runI use tests for the rules, browser checks for the interface and an installed phone for the experience.
iPhone TestFlight acceptedApp Store review pendingAs recorded in my project on 9 October 2026.
STILL BUILDINGWhat this chapter demonstrates
I am testing WGTakt in my own WG. The move in story comes from the recorded July test and its later fix. October checks are recorded app verification, and the iPhone acceptance is a user device report. For this showcase I reviewed the existing app code and tests. I did not rerun the WGTakt test suites or independently recheck App Store status. The chore board above is a local explanation of the rule.