5 ms·
> How does it compare with YourPriorities[0]? Your Priorities was one of our main inspirations at the beginning, as an open source software that also had a str
by andreslucena 8y ago
> How does it compare with YourPriorities[0]?
Your Priorities was one of our main inspirations at the beginning, as an open source software that also had a strong relationship with the municipal level, on their case Reykjavík (Iceland). The main differences are that on YourPriorities a user only discusses Proposals and has one way of supporting them, and on Decidim you have other kind of supports (for instance limiting how many votes an user can made) and other features besides Proposals (like Meetings, Results, Initiatives, Consultations, etc).
(Disclaimer: I know Robert personally since 2012 and he even came to our first anual meeting on Barcelona at 2016.)
> What are its strengths and weaknesses?
Strengths:
* Modular architecture: more than 15 community modules.
* Easy to upgrade (as a ruby gem)
* Multiple features: we try to allow any kind of participatory space (processes, assemblies, initiatives/petitions, consultations)
* Online / offline integration: through meetings with photos, documents, minutes and moderators with special permissions to create user accounts
* Multiple verification / authorization ways (SMS, sending a code through other ways, through municipal census on the case of cities, etc)
Weaknesses:
* At the moment could be difficult to install (it's a Ruby on Rails gem and generator so you
need some Rails knowledge)
* Multiple bugs (working on them)
* UX and accessibility could improve
* No mobile app (yet)
- robertbjarnason 8y agoHi Andres & all :) I guess the main differences with Decidim from the Your Priorities site are: The client is a progressive web app built with Web Components. Users can submit ideas as audio or video, not only text. AI features like a recommendation engine, machine translations, voice-to-text & automatic "toxicity" score calculated for all incoming content. We moved the API from Ruby on Rails to Node.js in 2015.