New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Details that will be featured on each app in the App Center #180

Open
luisivan opened this Issue Mar 27, 2018 · 6 comments

Comments

Projects
None yet
6 participants
@luisivan
Member

luisivan commented Mar 27, 2018

The App Center will have a view which is specific per app. Some ideas of what we could show:

  • App name + icon
  • Small description
  • Number of installs (I know this is a trickable metric, so not completely sure about it)
  • Capabilities/roles it would expose
  • Permissions it would require
  • Any other ideas?

I think most of it can be taken from arapp.json, right?

@onbjerg

This comment has been minimized.

Show comment
Hide comment
@onbjerg

onbjerg Mar 27, 2018

Contributor

No, arapp.json is the technical stuff, manifest.json is the human readable stuff.

From that file you can pull: app name, icon, small description.

For permissions and roles you would either use arapp.json or artifact.json (which is just an arapp.json with some extra machine data).

For number of installs we would have to have some sort of centralised service that scans for proxies with a specific app's appId. Not impossible, but a bit tricky I guess.

Contributor

onbjerg commented Mar 27, 2018

No, arapp.json is the technical stuff, manifest.json is the human readable stuff.

From that file you can pull: app name, icon, small description.

For permissions and roles you would either use arapp.json or artifact.json (which is just an arapp.json with some extra machine data).

For number of installs we would have to have some sort of centralised service that scans for proxies with a specific app's appId. Not impossible, but a bit tricky I guess.

@izqui

This comment has been minimized.

Show comment
Hide comment
@izqui

izqui Mar 28, 2018

Member

Number of installs is doable a PITA to calculate clientside

Member

izqui commented Mar 28, 2018

Number of installs is doable a PITA to calculate clientside

@jounih

This comment has been minimized.

Show comment
Hide comment
@jounih

jounih Mar 28, 2018

Any easier way to measure popularity?

jounih commented Mar 28, 2018

Any easier way to measure popularity?

@izqui

This comment has been minimized.

Show comment
Hide comment
@izqui

izqui Mar 28, 2018

Member

Explicit signaling/reviews that are stored on chain

Member

izqui commented Mar 28, 2018

Explicit signaling/reviews that are stored on chain

@lkngtn

This comment has been minimized.

Show comment
Hide comment
@lkngtn

lkngtn Mar 29, 2018

Member

Number of installs is doable a PITA to calculate clientside

This is something that can be snapshotted periodically by a computation oracle?

Member

lkngtn commented Mar 29, 2018

Number of installs is doable a PITA to calculate clientside

This is something that can be snapshotted periodically by a computation oracle?

@onbjerg

This comment has been minimized.

Show comment
Hide comment
@onbjerg

onbjerg Mar 30, 2018

Contributor

@lkngtn Theoretically. My idea is to have a small server that scans the chain and people could query that like a normal webserver. I don't see the clear benefit of snapshotting it on-chain since the data that is fed into the oracle would still come from a centralised source.

Contributor

onbjerg commented Mar 30, 2018

@lkngtn Theoretically. My idea is to have a small server that scans the chain and people could query that like a normal webserver. I don't see the clear benefit of snapshotting it on-chain since the data that is fed into the oracle would still come from a centralised source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment