Major Aragon releases always try to include big items that make the user experience qualitatively better.
This is A1’s take on the items that we will focus for this release.
Timeline: Mid-July
In scope
Visual revamp for the Aragon client
A visual revamp proposal is being worked on by our design team.
Fundraising app
Intro
As it was planned and designed since the very first versions of Aragon.
Initially, we thought on building a very basic fundraising app in parallel to Aragon Black’s, but we think that it’s a better use of time to focus on Aragon Black’s initiative too.
Action items
- Support Aragon Black’s fundraising app in code reviews and design needs
- Note: As this app will need a lot of state, caching is really needed
UI for the Agent app
Intro
Agent allows Aragon organizations to interact with other contracts as its own entity. However, Agent is just accessible through aragonCLI right now.
Action items
- Update the outdated design
- Update to latest design system
- Remove “browse dapps” tab
- Remove “external contracts” for now, just do token balances and past transactions
- Requires: at least a basic version of the Radspec registry
- Or at least the function name (e.g. how MetaMask does it)
- Integrate functionality to create transactions through the Agent into Frame. That will serve as a reference implementation for other signing providers to adopt
New onboarding
Intro
The current onboarding has some issues:
- There are just two templates, and they are a bit confusing for users
- Creating organizations requires two transactions
Action items
- Revamp the onboarding experience
- Revamp the onboarding templates
- We should include not only templates with the default apps, but also with the Fundraising, Pando and TPS apps
Email notifications
Intro
This becomes essential when organizations are holding important assets or funds. Even more so when the Aragon Court is out. We should look into ways of providing real-time notifications.
This will just be email, no desktop/browser/ push notifications for now.
Action items
- Implement a screen in the client as an app or as part of preferences
- Select which apps and events a user wants notifications on (a lot of apps organize this by "triggers" and "notification channel")
- Need email authorization flow for subscriptions (ask supplied email if they’d like to subscribe)
- Select which apps and events a user wants notifications on (a lot of apps organize this by "triggers" and "notification channel")
UX improvements to the Voting app
Intro
The current voting experience could be greatly enhanced by including UX wins from our Survey app.
There are some issues we have detected:
- The right panel is too small to display all proper information about a vote. Votes are important and should take the whole screen
- Users want stats of the votes over time
Action items
- Redesign app with survey UX
- Implement modifying suport and quorum
- Write human-friendly copies for support and quorum
Finance app features
Action items
- See https://hackmd.io/PplY9TuZRc-2txbZYGlTZA
- Show vault direct deposits and transfers
Permissions UX enhancements
Intro
Aragon permissions are what makes Aragon great and fundamentally different from old-school legal entities.
However, being quite a new paradigm, users struggle. We have collected great user feedback, and it feels like it’s time to enhance their UX.
Namely, they struggle understanding:
- Permission managers
- What permissions an app has, vs which permissions are set on it
- What are EVM scripts/kernel/other technical terms that are just mentioned in the Permissions app
Action items
We have collected great user feedback, and it feels like it’s time to enhance their UX.
Permissions should allow any user to intuitively understand what is the hierarchy and structure of any given Aragon entity.
Removed from scope
Aggressive caching
Intro
Loading an organization created 6 months ago and with more than 100 votings takes several minutes. This hurts user experience.
We should look for ways to make the first load almost immediate, and then increase trust over time when the client is able to verify more and more of the organization’s state. We could look into tradeoffs between centralized/decentralized.
Action items
- Research and implement centralized state caching solutions that gradually lead to a fully trustless state over time
Reason for removal: Bandwidth
Voting
- Allow to export votes in CSV
- Allow to see all votes casted / voting analytics
Reason for removal: Bandwidth
Finance
- Budget per token per accounting period
- Notify user in UI of their accounting expenditures (how much is left, possible to make payments)
- Important for users: No priority for payments, basically a race to get money out and other payments need to wait
- Recurring payments
- Pausing transactions:
- Right now the contracts don’t support fully removing payments, so they can only be “paused”
- Show all paused payments as if they were “archived”
- In the future we can add full removals in to the contract to allow users to “delete” payments
- Right now the contracts don’t support fully removing payments, so they can only be “paused”
- Investigate ways for an organization to analyze budgeting
- Investigate ways for an organization to analyze their expenditure
Reason for removal: Bandwidth
Optimistic UI
I think this is not that important with the Activity panel, but worth mentioning anyway.
Still needs design research.
Reason for removal: Bandwidth, design needed
Improved feedback for pending actions
Context: Showing Pending (Forwarded) Actions in Apps
Reason for removal: Autark will be the ones leading that effort
Meta-transactions
So users wouldn’t have to hold ETH or pay for transactions inside a given organization.
Reason for removal: Postponed since it needs smart contract upgrades, we will bundle them in a future release
Global kill-switch
Way to opt into an aragonOS global kill-switch that pauses contracts if a critical bug is found on them.
Reason for removal: Postponed since it needs smart contract upgrades, we will bundle them in a future release