# Polls UX: Problems and solutions

**URL:** <https://meta.discourse.org/t/polls-ux-problems-and-solutions/46722>\
**Category:** UX\
**Created:** [July 1, 2016, 7:18pm UTC](https://meta.discourse.org/t/polls-ux-problems-and-solutions/46722 "2016-07-01T19:18:52Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [July 28, 2016, 10:06pm UTC](https://meta.discourse.org/t/polls-ux-problems-and-solutions/46722/29 "2016-07-28T22:06:26Z")

</div>

After giving this more thought, I agree that:

> [@sam](#):
>
> the huge issue I have with that mockup is that it tries to be both “buttons” and “radio boxes”, pleasing both ends up pleasing neither.

However I do _not_ agree that using platform native controls is a good idea here. That’s like using platform native emoji, which leads to weirdness in interpretation and style.

So if we **remove the button style entirely** – which also has the huge advantage of doing away with that ugly, hacky “a green button means it is selected” style – and transition to the **font awesome glyphs for radio and check** , that’s a change I can support, and I no longer disagree with the rationale @claas.

 ![](https://global.discourse-cdn.com/meta/original/3X/1/d/1dfa9cd50757395c69960695f50a3bc7f23d08d7.png)

The behavior will still be button, e.g. clicking anywhere on that line will trigger a check or radio. Just the visual _style_ of button is removed completely in favor of the glyphs.

@tgxworld will be working on the essential change to de-button polls for 1.6.

---

_[View the full topic](https://meta.discourse.org/t/polls-ux-problems-and-solutions/46722)._
