aragon

We should apply sorting to the list of installed apps in the App Center (we "randomize" the discovery page to make it a bit more "fun"):

1. Upgrades available ahead of up to date apps
2. Alphabetical

cc @bpierre @dizzypaty I've also been wondering if it might be nice to start having sections in the App Center similar to Voting, for the different classes of apps (e.g. "ready" vs. "experiment

A few items left from the test suite advisory:

• Explicitly test AppProxyFactory. newAppProxyPinned(IKernel, bytes32)
• Explicitly test EVMScriptRunner.protectState modifier
• Explicitly test auth modifiers in apps (APMRegistry, Repo, EVMScriptRegistry)

We currently have some utilities copied from aragonUI in a number of the apps, but we should prefer directly importing them from aragonUI instead (for example, shortenAddress).

Currently, there is no support for overloaded functions in a smart contract. The functions are accessed via name only, which will only provide access to the last overloaded function in the abi.

This appears to be true for both the AragonApp and AragonApp.external(...) contract objects.

The first donate function in the contract below will not be accessible via the aragon-client:

c

There is no way to navigate the menu on mobile.

Confirmed on Android 9.0 smartphone

We use the fields in manifest.json in aragon/aragon and it's not obvious what is needed and what each field does.

🚀 Feature

Aragon apps used truffle-extract to extract information from Truffle's build files.

The new plugin would be a simple wrapper around this package to support the same functionality on the buidler ecosystem.

js-ipfs-api is huge

If we try to use this dependency, and it's not available, we should throw an error.