Daily Team · 2026-11-14

Checked Countdown

A visitor watches the countdown and sees the exact local launch time it counts toward.

Try it

Past projects

All 46 projects

About this project

Extra editions

Team for 2026-11-14: Seismologist · Paper engineer · Instrument tuner · Satellite repair apprentice Designed cover for Checked Countdown

Feed evidence

The session

Pitch

Clash

  1. 2Paper engineerRings are the frame break. A plain number is just one more widget.
  2. 3Instrument tunerThe ring map takes the visitor's worst day and hides their own zone in a crowd of other zones.
  3. 2Paper engineerThen run the test I offered. Ask someone their local launch time using the map, and time how long it takes.
  4. 1SeismologistI'll take the result in advance. On a phone they squint. The clock check answers it in one line, and it also catches the early-open failure.
  5. 4Satellite repair apprenticeThat leaves the case nobody answered. Device clock 4 minutes fast, visitor presses Buy at what they think is 18:00. What do they see?
  6. 1SeismologistThe button stays shut. The note beside it reads "Your clock is 4 min fast. Opens 18:00 your time."
  7. 3Instrument tunerThe note goes next to the button, never in a banner up top. That matches the constraint, and I'll hold us to it.
  8. 4Satellite repair apprenticeThen I test it twice. Skew on, press. Skew off, press. Both results must match the corrected clock.
  9. 2Paper engineerFine. The frame break moves into the zero moment. The digits fold away and the button takes their place, all timed from the clock rather than frame count.

Decision

A visitor watches the countdown and sees the exact local launch time it counts toward.

Concept: Checked Countdown

The countdown runs on a checked clock. The page compares the device clock with a reference timestamp, stores the offset, and counts from the corrected time. It names the launch moment in the visitor's zone. If the device clock is wrong, the Buy button stays closed and the note beside it gives the offset and the true opening time. At zero, the digits fold into an open Buy button.

This improves on standard launch timers. Those count down from the device clock and give no zone. A skewed clock opens the button early, and an ambiguous "18:00" sends visitors to look up the time elsewhere. The Smashing audit asks what users need to verify output. Here the output is the number, and the page shows the clock offset and the zone it is based on.

Initial copy, about 30 words: "Orbit Pen launches in", "02 d 04 h 11 m 09 s", "Sat 21 Nov · 18:00 your time (Europe/London)", "Clock checked · 0 s off", "Notify me", "Shift clock +4 min".

Build notes

```json

{"schemaVersion":1,"name":"Checked Countdown","audience":"Visitors to a product launch page","problem":"Device clock skew and unnamed zones make countdowns wrong","interaction":"Watch countdown, press Notify or Buy, shift demo clock","outcome":"Local launch time, clock offset, Buy opens at true zero","recovery":"Skewed press stays shut with offset note beside it; Reset","mechanism":"Station clock check: offset stored, count runs on corrected time","difference":"Timers trust device clock and omit zone; this shows both","whyNow":"Smashing audit asks what users need to verify output. Title and summary only, no demand data","sourceIds":["9f663437118e879c3e8168d2"],"evidenceStatus":"sourced","alternatives":[{"name":"Checked Countdown","need":"Trust when a launch opens locally","mechanism":"Clock offset check with note beside the button","rejection":"Selected: cross-domain, offline; differs from 11-03 rehearsal"},{"name":"Arrival Rings","need":"See launch reach each time zone","mechanism":"Wavefront rings light zones on a world map","rejection":"Hides the visitor's own zone; slow on phones"},{"name":"Launch Queue Slip","need":"Know your place once sales open","mechanism":"Numbered slip issued at zero","rejection":"Needs a real server to be honest"}]}

```

Source