All originals
Social schedulingShipped 20255-week sprint

WhenWouldWork

The hour that works for everyone, without the group chat.

Scroll for the technical layer
Layer 01 — The world

Nine clocks converging on a single amber hour inside a dark coordination grid.

A group scheduling tool that turns nine calendars into one agreed hour. No polls, no threads, no third app to install.

Interface01
Motion02
System03
Layer 02 — The build

X-ray the interface. See the engineering.

The challenge

Group scheduling dies in the group chat. Every existing tool added a poll, and every poll added a decision nobody wanted to make. The real problem was trust: people did not believe the proposed time was actually free for everyone.

Architecture decisions

  • 01A single availability graph per group, computed server-side from read-only calendar permissions.
  • 02Time proposals are derived, never stored as separate objects, so there is one truth per group.
  • 03Optimistic local confirmation with a conflict reconciler that runs on reconnect.

Build process

Week 1Twelve founder interviews. Killed the poll model on day three.
Week 2Prototype: one screen, one proposed hour, one tap.
Week 3Availability graph and conflict reconciler.
Week 4Calendar permissions hardened, empty states rewritten.
Week 5App Store submission, instrumentation, launch.

Stack

Client
React Native · Expo
State
Single derived availability store
Backend
Postgres · edge functions
Calendar
OAuth read-only, iOS & Google

From the codebase

// One truth per group: availability is derived, never stored twice
const hour = deriveAgreement(group.availability, {
  window: "next-7-days",
  preference: "evening",
});

Measured results

3

taps to a confirmed time

68%

fewer coordination threads

2.4×

faster group commitment

The technical layer holds the challenge, the architecture decisions, the week-by-week build and the numbers. Open it when you want to judge the engineering, not the screenshots.