Skip to content
Doorbell

Changelog

What changed, and when

Doorbell is built in the open, in small releases. Each entry says what you can now do; dates are the day the release went live.

  1. Analytics, link health, abuse protection and onboarding

    • Analytics dashboard: workspace and per-Link reports with opens, unique visitors, QR share and destination clicks; breakdowns by source, country, device and operating system; a home overview with a seven-day chart, top Links and a needs-attention list.
    • Link health and notifications: destinations are checked in the background; two failures in a row mark a Link as broken and notify you; it recovers on the first good check.
    • Abuse protection: destinations can be checked against Google Safe Browsing, suspicious Links show a warning page before redirecting, and anyone can report a Link from there.
    • Onboarding: two optional questions, then your first Link, made inline.
    • Bundle button presses are now counted as clicks, not opens, so page analytics stay honest.

  2. First release: Links with two doors, and the controls behind them

    • Short links and QR codes from one Link; the QR encodes the short URL with a scan marker, so scans and taps are reported separately. SVG and PNG export.
    • Change the destination after sharing. Every change is a version with a summary; restore any earlier version.
    • Rules builder: WHEN conditions (country, device, operating system, date range, time window) and THEN destinations, in order, first match wins, with a test-visitor tool.
    • Schedule presets: switch on a date, or repeat by time of day in the Link's timezone, with a right-now and next-change summary.
    • Access and expiry: expiry presets, open limits, one-time links and passwords, with a choice of what visitors see afterwards.
    • Pages and bundles: six templates, blocks (heading, text, image, button, link list, divider), token-based appearance and a live preview through the same renderer visitors see.
    • Redirects served from a cache at the edge, answered with 302 and never cached by browsers, so a change is honoured within seconds.
    • Privacy-preserving analytics from day one: hashed daily visitor keys, city-level location, bots recorded separately.