Client: Show contract versions somewhere in the client

[john-light]

Describe the solution you'd like
For debugging purposes it might be useful to know what version of Aragon contracts people are using in their org e.g. aragonOS and the various apps plugged into it. The Settings app seems like the best place to put this for right now.

[izqui]

I would add this here: https://github.com/aragon/design/issues/17 cc @jounih

[jounih]

I've got app versions showing on the app centre design that @izqui linked to. If we need something quick for showing app versions before the app centre gets built, we could just add the versions below the contract address badges in current Settings app.

Not sure if it would make sense for AragonOS to be in that list or in its' own section in Settings?

[sohkai]

Not sure if it would make sense for AragonOS to be in that list or in its' own section in Settings?

It should be the version tied to the "organizational address", as well as any "internal apps". We'd have to think about how to show these non-UI apps though.

[jounih]

Cool. I think adding 2 subcategories to "Aragon apps" here would perhaps be the way to do this - one for the UI apps, and one for the "System apps" or "Internal apps" - I've called them "System apps" in the mobile permissions design

[bpierre]

If we need something quick for showing app versions before the app centre gets built, we could just add the versions below the contract address badges in current Settings app.

Not sure it would be enough in that context, but we will have them in the app badges: https://github.com/aragon/design/issues/21

[jounih]

If we need something quick for showing app versions before the app centre gets built, we could just add the versions below the contract address badges in current Settings app.

Not sure it would be enough in that context, but we will have them in the app badges: aragon/design#21

Ah yeah that would be cleaner, just list all app badges in "Installed apps" in settings (for now), and you can click on them to show the contract address. I'll mock it up (with the "System apps" too)

[jounih]

Design with app badges-

https://github.com/aragon/aragon/issues/492#issuecomment-467841964

I'm wondering what's the best word for apps without UI (ACL, Vault etc).. "System modules"?

We were talking with @bpierre about separating these from the apps in Permissions too, under a different heading. In user testing people have been feeling a bit anxious about seeing "ACL", "Kernel" etc in Permissions, so I suggested we hide them by default, and show a button "Show system modules" in permissions that then expands the list to show them.

[john-light]

I'm wondering what's the best word for apps without UI (ACL, Vault etc).. "System modules"?

@jounih right now I think we just call them "default apps". Before renaming them to something else I think it's worth thinking about what distinguishes them aside from not having a UI, and what implications there could be for renaming them.

For example, Agent app does not have a UI yet. Does this make it not an Aragon app? And what if someone develops an alternate ACL or Kernel that is still aragonOS compatible. Would that go under "system modules"? What if someone does make a UI for one of the system modules?

Did you investigate at all _why_ people feel anxious about seeing the ACL and Kernel sections in the Permissions app? Is it the name? Is it because they don't know what these apps do, or what the implications for changing permission settings on these apps are?

Knowing the answer to these questions would help us make an informed decision about how to address the anxiety and how we should go about renaming these components, if that is the best thing to do.

[jounih]

@john-light good thoughts, let's open up another issue for that.

This particular issue (Show contract versions somewhere in the client) - will be solved with the app center that shows contract versions, so I'm closing this one