Build in Public
Build in Public
3 min read

Feature requests megathread — the community roadmap

Opening a standing thread for ideas that later shipped: multiple recipients, subjects, attachments, and more.

A place for the backlog

The same day as the welcome post I opened a feature-requests megathread. The goal was simple: one place for small tweaks and big ideas, so I could read everything and let community priority shape what came next.

That thread became the informal roadmap. Later BIP chapters often cite requests that first showed up here.

Ideas that shaped the product

  • Multiple recipients — asked early (May 2025) so people could add backup inboxes or share a letter; shipped in July (chapter).
  • Custom subject lines — requested midsummer; shipped in August (chapter).
  • Attachments / media — requested from the welcome post onward; shipped New Year’s Eve 2025 (chapter).
  • Longer horizons & smarter dates — random/duration-style scheduling wishes fed the 10-year limit and later date UX work.
  • Keep the surprise — several people asked us to preserve sealed capsules; that constraint stayed a product principle.

What I took away

The megathread also carried a lot of thanks and sustainability questions (“how long will it stay free?”). Those comments foreshadowed the later pricing and credits chapters — quality of service matters as much as feature velocity.

I treat this thread as living documentation: new ideas still land there, and shipped features get their own announcement posts linked from this archive.

From the community