Propose new features
Designing Decidim together
Vote multiple times for a same project
UPDATED ON APRIL 8, 2021
Is your feature request related to a problem? Please describe.
With the actual voting systems on participatory budgets, users can vote according to a percentage of the total budget, or with a min or max of projects to be voted on. The problem is that they can't express any preference for a specific project by granting it several votes.
As a user voting in participatory budget process, I want to express different levels of support to the projects I'm voting for.
As an admin I might want to implement rules to register that information and adapt my vote tally accordingly.
Describe the solution you'd like
Admin side (see mockup)
The creation of a new voting rule taking as input 2 parameters :
- The total number of votes available to each user;
- The maximum number of votes that can be allocated to each project;
This new voting rule is not compatible with the current existing rules.
It will be necessary to remove the check that blocks the selection of a project several times by the user to develop this functionality.
User side
This is where the complexity in term of UX of the implementation lies.
We set some preliminary constraints upstream:
- The interface must work on any type of device;
- The interface must be accessible (RGAA);
- The interface must adapt to different values set in the parameters of the rules;
- e.g.: if the number of votes authorised per project is set to 10 or 20, it shoudn't be a problem for the interface.
The project index
In addition, the Decidim product team has decided to simplify the interface for the proposals cards, vote buttons will no longer be displayed on the cards to reduce the amount of info shown to users.
This applies to budget project, we plan to anticipate this evolution as part of the development of this functionality. See mockup for projects index.
The voting interface
We investigated 4 types of interfaces for this user interaction :
- Incremental vote buttons
- Input steppers
- Star ratings
- Sliders
See the mockups attached. Our team is in favour of implementing the input steppers as
- they scale well if many votes can be given to a single project,
- the increase / decrease vote allocation interaction is clear for user
- the budget order is built like an e-commerce order, input steppers are widely used to set quantities
Does this issue could impact on users private data?
No
Related links
Token voting rule on Budget component (External link) (withdrawn)
Provide new option to support a proposal: with a scale (External link)
A study conducted by Toulouse about voting methods on participatory budgeting (External link) (in french)
Funded by
Toulouse
List of Endorsements
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
View all comments
Conversation with Pauline Bessoles
Hi to all following this proposal!
I made a second iteration of what this feature would look like in BE and in FE (on the projects index).
You can find the mockup here: https://www.figma.com/proto/SjLsHxOSVsNUn71d1PQpn9/Metadecidim?node-id=8%3A176&viewport=703%2C436%2C0.10763725638389587&scaling=scale-down-width
The idea here is to create a new separated voting rule, that wouldn't be compatible with the others.
@ahu After iterating on the eventuality of making this feature compatible with all the voting rules, I'm afraid that would be really confusing, for the admin and for the users. Tell me if you want me to post them here!
Looks really good to me @Pauline !
One thing I'd like to add would be a button/link to remove the project from the vote next to the project controls on the right side. I guess it could be also just an [X] button at the top corner with a screen reader label attached to it.
It would be also good to think how this will align on mobile. Especially among the youth, mobile usage is around 70-80% of the users and the budget voting view we have right now is not very understandable on mobile.
I understand the complexity related making it compatible with the budget based voting. I haven't heard of such request yet, so I think it's probably OK making it a separate rule.
Thanks for your feedbacks, I forgot to add the remove button! I added it in the previous mockup, tell me if you think that's understandable for the user.
You can find the mobile mockup here : https://www.figma.com/proto/SjLsHxOSVsNUn71d1PQpn9/Metadecidim?node-id=47%3A981&viewport=510%2C436%2C0.1859215945005417&scaling=min-zoom
Yes, remove button works well. 👍 I'd make it slightly larger, though.
Regarding the mobile, I'd like the buttons to be much bigger. Now they go very small after one project is selected.
Apple suggests mobile touch targets of at least 44x44px and Android suggests minimum of 48x48dp (dp = visible pixel).
https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
https://material.io/guidelines/components/buttons.html#buttons-style
Apple's recommendation is also a WCAG success criteria:
https://www.w3.org/WAI/WCAG21/Understanding/target-size.html
Loading comments ...