If it doesn’t, we could consider using a monospace font for addresses and timers @jounih

If it doesn’t, we could consider using a monospace font for addresses (and maybe timers) @jounih

Sweet, yeah, for ease of reading I think giving the same spacing would be helpful

yeah totally

I have noticed this as well, I’d love to see some design proposals for using a monospace font for addresses

@bpierre would it make sense to hide the You label when the user sets a Custom Label to their address?

IMO yes, we should hide it because it becomes redundant

@dizzypaty I agree:

even better:

is this the new paradigm for left nav icons?

I know @adria has been working on new more colorful icons for the sidebar to match the icons used in the app center… but I don’t know if it is a new paradigm – I hope that we have a process for changing design guidelines that impact third party devs and don’t make that change lightly…

personally a big fan of the grey icons and hope they dont go away.

@yalda Yes, the colour versions are the new recommendation; we’ve chosen them for higher visibility over the “system” apps, which will stay grey.

We will have a page on the developer portal soon with specific recommendations: https://github.com/aragon/hack/pull/125/files

I was thinking that maybe it makes sense to hide the “connected to network” sign until there’s no connection or the user is in a different network than the one the DAO is in

cc @dizzypaty @yalda

I wonder what made you think this way, could you develop a bit on the rationale? I personally think that it’s important to indicate the network status at all times, so users are reassured of it working well, and they recognize the position and UI element they need to look for when there’s a connectivity issue. Also, we have some designs that Jouni did for a ‘network status popover’ that gives more information to users in case of an issue and I think this can be very useful too: https://www.figma.com/file/TRyOTNyTIqcqLM9yANDFq2Ia/Network-status?node-id=0:1

We need to work a bit more on the style of the indicator itself and how we combine it with the currently connected account, but I think it’s worth keeping it.

I wonder what made you think this way, could you develop a bit on the rationale? I personally think that it’s important to indicate the network status at all times, so users are reassured of it working well, and they recognize the position and UI element they need to look for when there’s a connectivity issue. Also, we have some designs that Jouni did for a ‘network status popover’ that gives more information to users in case of an issue and I think this can be very useful for troubleshooting: https://www.figma.com/file/TRyOTNyTIqcqLM9yANDFq2Ia/Network-status?node-id=0:1

We need to work a bit more on the style of the indicator itself and how we combine it with the currently connected account, but I think it’s worth keeping it.

I think it’s the principle of “everything is working well unless it’s not” and alerting the user when it’s not

Wondering what you all think of my card design for Range Voting – I think the way the Voting card is designed with the data being outside the card can especially be confusing on which card it’s related to.

https://projects.invisionapp.com/share/FWR85XSQ6SA#/screens

Wondering what you all think of my card design for Range Voting – I think the way the current Voting app card is designed with the data being outside the card can especially be confusing on which card it’s related to.

Wondering what you all think of my card design for Range Voting – I think the way the current Voting app card is designed with the data being outside the card can especially be confusing on which card it’s related to when on mobile.

Wondering what you all think of my card design for Range Voting – I think the way the current Voting app card is designed with the data being outside the card can especially be confusing on which card it’s related to when on mobile. (Note: we don’t have “View Vote” bc you can click on the card to open the vote).

@luis I think we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page. I agree that hiding it works, and showing a top notification bar would help the user troubleshoot better. On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I think we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page [but perhaps that is complemented to implement due to the wrapper. i would actually add a top bar though in general, for system wide activities). I agree that hiding it works, and showing a top notification bar would help the user troubleshoot better. On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”

@luis I think we especially need to notify the user if one is on a different network than the DAO or not connected – I usually like this being a prominent bar at the top of the page [but perhaps that is complemented to implement due to the wrapper. i would actually add a top bar to the wrapper in general, for system wide activities). I agree that hiding it works, and showing a top notification bar would help the user troubleshoot better. On many occasions I have not noticed why things aren’t working and been like “oh duh I need to change my network”