Which Beeminder feature/project will have the highest ROI?
Basic
19
Ṁ6916resolved May 1
100%73%
[AUTOD] Steadily adding integrations (Focusmate has been So Huge!); in particular the meta integration
19%Other
1.4%
[UNCLE] The uncle button (as in crying uncle, like "yes yes, stop zeno'ing, I'm intentionally taking the derailment on this")
0.0%
[SCHED] Revamping/optimizing the pledge schedule
5%
[BOARD] Just gradually making Beeminder better and clearer and onboarding better and emailing people more when they fall off the wagon, etc etc
1.2%
[GRAPH] Dynagraphs, aka merging graph.beeminder.com into Beeminder proper
0.0%
[STAIR] Bright Red Staircase
0.0%
I think you'd get more engagement if you explained the features you've got. Right now, searching this is a Trivial Inconvenience.
0.0%
An unlisted feature
In the absence of a better way to estimate this, we'll go by what we decide to do first.
This question is managed and resolved by Manifold.
Get
1,000
and3.00
Sort by:
Yeah, the average is 3-ish per year while you've now (tentatively) committed to 5. The freeCodeCamp integration was long enough after Focusmate that it was sort of a continuation of the status quo, but since the description specifically mentions what you *decide* to do first, it looks like that decision's been made and the market should resolve.
Well that bounty market worked brilliantly and now the answer is that we totally do have a graph: https://www.beeminder.com/meta/integrations
We don't have a graph! But the data from which to make one is here: https://beeminder.consider.it#done-11
I agree that the market shouldn't resolve yet. The answer says "Steadily adding integrations".
I don't know how Daniel defines "steadily adding". But, if I were him, I would say that someone shows signs of "steadily doing X" if they consistently do X over an extended duration.
Is there a graph somewhere that shows the total # of Beeminder integrations on a weekly or monthly basis?
@M, agreed about confusing "highest ROI" with "best feature". For example, UNCLE is a plausible contender due to how easy it should be to implement.