Open johannesmoormann opened 2 years ago
Zerion.io are using Beamer for their changelog updates. It has an API to gather user feedback on each update. And an embeddable UI widget.
My research doc on an issue. @DiogoSoaress when you ready lets share ideas. https://docs.google.com/document/d/1z_hJ7eVMiSnCLEpQNAqwuDZn3ewMaxHWyi9rIE-b2Go/edit#
Adminstration (effort, Github intgeration) Costs Implementation effort trade offs Cookie issues/Datenschutz (marketing etc.)
Intercom functionality list, I will work on solid proposal on implementations https://docs.google.com/spreadsheets/d/1mUXFAVZSROVj6kcMz3wvaUCw49cwBDpxyWs3FZXDlAw/edit#gid=0
Problem Owner
@DiogoSoaress @liliiaorlenko
Part 1: Define the problem
What problem are you trying to solve?
Without reading the release notes, a user cannot easily discover new features that have been introduced.
What is your hypothesis?
If we solve this problem, new features will see increased usage and experience the progress the product is making more directly.
What value does this bring to our customer and/or our mission? What is the goal?
You can build the greatest feature, but when the user does not know about it to a satisfying degree it e.g. how to enable/disable prefixes in the web interface, the impact of the feature will be limited while the experience of the user could have been improved.
How do we measure it?
No. of feature requests for existing features Usage analysis User interviews
Links:
Research document: https://docs.google.com/document/d/1z_hJ7eVMiSnCLEpQNAqwuDZn3ewMaxHWyi9rIE-b2Go/edit#
Meet Beamer! https://www.youtube.com/watch?v=zQx5_STdzg0
Part 2: Shaping the problem
Possible Solution(s)
After looking at different tools to communicate changelogs and how other players have approached the problem of feature discoverability, a full fledged product seems to offer advantages over a in-house implementation straight off the bat.
The way of showcasing "new features" is highly customizable, plays well cross platform and allows integrations with 3rd party software (like GitHub) through an intermediary automation product like Zapier (see plans https://zapier.com/app/billing/plans)
Given its high adoption and online resources, one of the most attractive solutions could be Beamer as it is very customizable.![Screen Shot 2022-01-26 at 17 20 13](https://user-images.githubusercontent.com/32431609/151202885-ed288c1b-a537-4d5a-99ba-8d27d27fbf02.png)
The paid plans can be assessed here https://app.getbeamer.com/billing
Content management is done through their platform or API
Rough Scoping & Timeline
It is expected that its integration is smooth based on the documentation and active support and it could be integrated in a first phase as a Proof of Concept.
Risk(s), Key Trade Offs & Decisions
One of the Beamer plans (the PRO) provides services up to 10.000 visitors per month. Their support told me that they count unique users with a cookie but alternatively we can send a _userid to identify a single visit. This cookie is not for marketing purposes but only to track reads (knowing how many unread posts) and visit counts.
In the Enterprise plan we have a way to implement Beamer via API and a sandboxed iframe to avoid any cookie if necessary.
Alternative external solutions
Alternative internal solutions
Concept Mocks
With Beamer:
Open Questions