🪴 Scaling Synthesis

Search IconIcon to open search

I- Search terms as the basis for user-defined notifications

Last updated June 25, 2022

Authored By:: P- Rob Haisfield

In multiplayer applications that do not have native notifications like Roam Research, we noticed a compensatory pattern in user behavior. Essentially, they would come up with a convention for a special page link to indicate a mention (like [[@ Rob Haisfield]] or [[mention: Rob Haisfield]]), and then write two queries for seen and unseen mentions. Unseen mentions would be filtered out through the addition of a link like [[seen]].

This actually isn’t far off from a proper notifications system. Its primary problem is that it requires the user to manually visit the location of the queries. The main adjustment would be to ping the user when a new item enters the unseen query. Roam users have hacked around this by writing plugins that would ping them on Slack whenever there was a new mention.

From a primitive design perspective, users would need the ability to set up automations, to include “new result enters query” as a trigger, and “send notification” as an action. From there, the user could define what would notify them by adjusting search terms. This is further enabled by composable queries.

It is important to note that not everyone wants to go through the effort to create their own notifications system, hence the importance of smart defaults. Notification through mentions is unlikely to be controversial as a starting point.