Task: Subscribe

Context

For the project, not only initial visits are important, but also the ability to bring the user back after the introduction of new mechanics, materials, and directions.

We need a simple "Subscribe" mechanic that does not interfere with the main interaction and does not turn the site into a funnel.

What needs to be developed

• determine what exactly a subscription means in the product;
• decide what updates users can subscribe to: the entire project, a specific domain, topic, blog, mechanics, or other entities;
• determine the minimum required set of data for a subscription;
• design a login without unnecessary registration, if possible;
• determine notification channels: email, Web Push, and other suitable options;
• integrate the subscription with the already planned Web Push infrastructure where appropriate;
• design subscription confirmation and management;
• provide the user with an easy way to unsubscribe;
• determine placement points for the "Subscribe" button;
• do not place the subscription before the main product and do not block access to content with it;
• provide an opportunity to subscribe after a useful interaction, when the value of the project is already clear;
• design return analytics and the effectiveness of various channels.

Principle

Subscription should appear as a voluntary continuation of interest:

"This is useful to me — let me know when more appears."

It should not become a mandatory step to access the main mechanics.