sonio

Right, but these filters are not quite trivial. How would you filter (MRR by Upvotes, MRR by comments and subscriptions or all). I think it depends, that's one of the reasons I have implemented an impact score combining MRR, user engagement and so.

It's just more simple to filter. Therefore, a feedback item with 10 upvotes can have an impact score of 40, while a feedback with 100 upvotes can have an impact score of 3.

Yes canny is more portal based whilst Sleekplan is more focused on a widget basis, you can interact with via $sleek SDK (so that it feels more integrated)

I am totally with you when you say that there is a chance that feature voting will backfire for the whole process. It depends on how you use it.

1. You shouldn't rely on up- and downvotes for feature priorisazion for example. Like I did for "impact scoring" at Sleekplan you could use factors like interaction of users, time staying on an item.

2. You shouldn't ask for solutions or features, You should ask for problems, issues missing functionalities and then collaborate (e.g. in the comments) to find a good solution that's satisfying everyone.

I currently writing a best practice (from my point of view) for the Sleekplan docs.

But having been in this orbit for some time I think that's simply a function of how teams want to handle feedback requests since everyone's needs are a little different.

That's really a good point, I like the idea of the slider solution! Maybe with some tiered pricing, that would also make it very easy to explain.

I think a limit on functionality would not go over so well since you have to pay for it and then getting limited by tracked user plus functionality.

Thank you! It started out as a personal page so I didn't think about it first. For the time being it will remain free of charge. The costs for the hosting are very low, because the architecture as SPA is resource saving. In the future, new features may be added in a paid subscription.