Why Beeper Should Become Truly Link-Friendly
A Next Step in its Integration Vision
Over the past few years, Beeper has set itself apart as one of the most integrative messaging platforms, uniting over 10 chat networks into a single interface.
Yet there is a crucial dimension of integration that is still largely missing: linkability — the ability for any message, thread, or conversation in Beeper to be reliably and automatically referenced (linked) from other tools. In other words: Beeper is not yet link-friendly.
For the Hookmark community, this gap is keenly felt. Our users routinely want to connect chat content with external apps, documentation, notes, task trackers, or reference systems. They want to be able to “hook” into a conversation — to reference it, jump into it — just as one might link to a document, a file, or a database record. Many of our users have contacted us to request integration with Beeper — something we can’t do until Beeper becomes link-friendly (i.e., provides basic linking automation).
Why Linkability Matters
Seamless cross-tool workflows. All serious productivity users craft workflows that span multiple apps. When Beeper remains a “black box” — great for chatting, but not for referencing — it causes friction and prevents more powerful automations.
Fulfillment of the integration vision. Beeper already has a developer API / desktop REST API for accessing chats locally (on the device) and bridges / intents for external apps. (see Beeper Developers).That already establishes the infrastructure to integrate. Enabling linkability is a logical extension of that, not a radical departure.
Alignment with the Manifesto for Ubiquitous Linking. The Manifesto, which was originally co-signed by 24 Mac app developers and thought leaders and has been signed by many more knowledge workers since then, argues that modern software should provide both a user interface to obtain a link to any “resource” (i.e., a “Copy Link” menu item) and an API to construct or resolve those links. In general, the manifesto signatories call for every app — including messaging systems — to expose stable URIs (or URN schemes) for their internal content, so that automation, apps, and users can reliably reference them.
Network effect and platform stickiness. Once Beeper becomes linkable, it becomes more deeply woven into users’ ecosystems. It transitions from being just another messaging hub to becoming a first-class node in users’ personal knowledge graphs. That adds stickiness and value.
The Manifesto for Ubiquitous Linking spells the rationale for ubiquitious linking in greater detail.
How to provide a linking API
We at CogSci Apps have provided Complete Information for Developers to Make Their Apps Linkable. We are available to answer any questions developers may have.
In sum:
Each chat, thread, or message should have a stable internal identifier and a link form (e.g.
beeper://thread/<id>orhttps://beeper.app/thread/<id>).The API should support resolving a link (given the link URI, navigate the user’s instance to that content).
The UI (on desktop and mobile) should allow “Copy Link to Conversation / Copy Link to Message.”
For end users, the link forms should be shareable across apps (e.g. paste into a note or task), and those links should work (open Beeper, navigate to the content) if permissions allow.
Given that Beeper already offers a REST API and bridges, the overhead for exposing a linkable interface is quite minimal— it’s an evolution, not a revolution.
Beeper would then join a growing number of developers who heeded the call and made their apps link-friendly. For example, Mimestream, the awesome gmail Mac app, became link-friendly in March 2024.
Call to Action
I call upon the Beeper / Automattic engineering and product teams to adopt linkability as a formal priority. I believe this feature would delight power users, strengthen integrations, and reinforce Beeper’s role as a connective hub.
To the Hookmark / broader productivity community: I encourage you to join me in requesting linkability from Beeper — email them, upvote related feature requests, reference this article. Collectively, we can help accelerate this next step towards ubiquitous linking.
We have deep links/linkability on the roadmap!