We would like to share with you a small summary of our experience at ETHWaterloo and the feedback we have gathered during the event.
Our strategy was twofold:
- Propose various project ideas based on Aragon and DAOs in general on ETHWaterloo’s forum and the Discord channel, then help the teams who choose to work on those ideas, if any.
- Sit down with teams during the hackathon and show them a quick demo on how they could create their dapp using Aragon and the benefits of doing so.
Overall, one team built their app with Aragon and we discussed and demoed our tools with several others.
There was confusion regarding what the teams could modify (i.e. the app itself) and what they couldn’t (i.e. the general menus, side panels, etc.). A surprisingly high number of people wanted to fork the Aragon client to have more control over the whole experience.
Another regular comment we received was that people wanted their own app domain name and not be restricted to an Aragon subdomain. One team also experienced technical difficulties with the
aragon-cli tools. The installation process was taking too long for them.
As for the positive feedback, developers unanimously loved the Aragon UI. They said it was intuitive, easy to use and beautifully built. There was also a universally positive response regarding the various aragonOS components and the benefits they provide, like built-in app upgradability and the powerful control logic of the ACL. Great interest was also expressed for some of the apps as well, like the voting and fundraising apps.
Almost all the teams would have been more than enthusiastic about integrating some of those components or apps into their project if it were possible to select them individually. Ideas in this discussion are very much in line with requests we have seen during the hackathon.