Should reactions replace simple upvotes on replies?

Priya Nair Priya Nair 3 months ago

With reactions now available in Pro, I am wondering whether plain upvotes on replies still earn their keep. Reactions carry more nuance — heart, rocket, hooray.

Do you think both should coexist, or does that clutter the UI? Curious how others reason about this.

3

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

Strong agree. Good defaults beat a wall of toggles every single time.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.

Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.