3 ms·
Super neat! A count at the top of each item would be cool (ie quick glance see counts of yes / no, maybe shaded by party affiliation?) On mobile I wouldn’t mi
by bix6 2y ago
Super neat!
A count at the top of each item would be cool (ie quick glance see counts of yes / no, maybe shaded by party affiliation?)
On mobile I wouldn’t miss follow profile / like comment, at least as a casual user when scrolling through a prop.
- blululu 2y agoI think that a tally of endorsements or partisan affiliation is counter productive. That is just a bias toward whichever side had the most interest groups pushing an agenda. Democracy works best when people think for themselves. We defer to the majority opinion after all the votes are tallied and not before.
- daisystanton 2y agoThanks so much for the feedback! Yeah, echoing another comment: we tried so many rounds of tallies/counts, because visual summaries are so useful from a UX perspective. But there are so many things that quickly start looking partisan. For example: we want to both a) be inclusive and let anyone share their choices as a voter guide, and b) not have visual summaries be a reflection of whatever biased population of users might be using OpenBallot at any time. (Some users gave us early feedback that they thought the visual summary was OpenBallot's recommendation of how they should vote, which we definitely didn't want.) In general, we're being really conservative with UI atm because we don't want to put ourselves in the position of doing any editorializing that smells partisan. (We even have two sorting methods for guides, one of which is "random", because it's tricky to balance making the big-name guides that people expect discoverable vs hard-coding a sorting method, which we'd prefer not to do, since even that feels partisan). We've got reams of detailed examples of these types of problems, so if anyone is interested, jump in on Discord! :-)