My earlier analytics showed 31 extension_installed users, 17 extension_open users, and 9 users with at least one successful action. That changed what I chose to build next.
- The biggest issue was not attracting zero users; it was helping users finish.
- AnkiConnect push succeeded 5 times out of 21 starts in that measurement window.
- Citation import and bulk links also failed when prerequisites were unclear.
These are small-sample observations from the earlier measurement window, not proof of product-market fit and not a claim about 1.1.3 performance.
The next useful metric is not another install. It is one more person completing the action they came for.
I built NotebookBloom around this workflow: https://notebookbloom.com
Top comments (2)
Measuring "successful action" instead of installs is the right unit, and 5 of 21 AnkiConnect pushes is a very clear place to start. When prerequisites are the failure, a preflight check helps more than better docs: detect that Anki isn't running or AnkiConnect isn't installed, and say exactly that, with the one fix, before the user clicks push. A failed action with a vague error costs you the user. A blocked action with a precise reason usually doesn't.
That’s the gap. I’ve already separated “can’t reach Anki” from “connected, but the cards failed,” with .apkg as the fallback. The check still happens after the click, though. Moving it earlier and measuring whether it improves that 5/21 baseline is a much cleaner next test.