search

aragon / design

UI/UX designs for the Aragon client and associated apps
Creative Commons Zero v1.0 Universal
30 stars 5 forks source link

AddressBadge component #3

Closed jounih closed 5 years ago

jounih commented 6 years ago
screen shot 2018-10-18 at 12 28 45

A new proposed design for an address badge component, to be used whenever an entity name/ethereum address is need to display on the Aragon UI.

The design follows the initial proposal by @bpierre - https://github.com/aragon/aragon-ui/issues/156#issuecomment-385998267

The rationale is that it should be very easy for users to visually distinguish in the UI when an entity is being referred to, and effortless to find out more information about that entity.

We allow shortening of long entity names/addresses where space doesn't allow for the full address, and by making the badge clickable we display the complete Ethereum address, make it very easy to copy the address, and make it easy to open the Etherscan url in another tab for more information.

luisivan commented 6 years ago

Something I was thinking: maybe emoji combinations, like the one Telegram uses (https://telegram.org/blog/calls) would be more user friendly than identicons. Thoughts?

stellarmagnet commented 6 years ago

Looking forward to this component!

1) Some thoughts to help with "DAO founder doppelgängers" is to also have some kind of special "verified" (Twitter-like) badge, so then for example, let's say I am an ANT holder, we end up knowing who the real "Luis Iván Cuende" really is, and someone else can't assume his entity when creating votes and tricking people into thinking it was Luis who created the vote.

Relating to this, we may want to also set a specific permission for who in the DAO can grant this "verified" badge to other people too?

Perhaps the DAO founders can be the initial set of "identity validators" / people who vouch for other identities within the DAO (I know this adds some element of centralization, but we all know very well how much of a problem identity is on Twitter).

2) Can you explain the design reasoning for why the address in the popup has a blue background color? Is it only blue once the copy to clipboard icon is clicked, or is it always meant to be blue like this? image

luisivan commented 6 years ago

I'm 99% sure that the background is only blue when selected to copy @stellarmagnet

stellarmagnet commented 6 years ago

Does the current architecture support autocomplete throughout all Aragon Apps for the "Recipient" address fields, tying it to the Identity app, or do enhancements need to be made to support this paradigm?

luisivan commented 6 years ago

Aragon UI will provide this component which will take care of everything for developers :+1:

stellarmagnet commented 6 years ago

I'm trying to find out more details because i'm wondering the complexity of integrating another app to read data from, to populate the autocomplete (e.g. one of the apps part of our planning suite - Address Book, which is useful for managing frequently used addresses of non-DAO members - which can be individuals, projects, multisigs, etc)

luisivan commented 6 years ago

I think that would be totally doable. In your local DAO settings, you could select identity registries that you wanna be able to autoselect from

tayvano commented 6 years ago

Truncation should be 0x + first four characters + ... + last four characters.

luisivan commented 6 years ago

Totally agree @tayvano! That's what we are using now for the product, but seems like the mockups weren't updated. Thanks for chiming in!

jounih commented 6 years ago

Ah yes this has already been updated in sketch file but had the old jpg here - updated :) Thanks for noticing!