[Joe here, on proxy account]

I think that this is valuable in general, but could be a lot more valuable with a more focused approach, rather than "more nodes". Specifically, I'd like to see the development of some middleware with a bit of logic in it to provide a better API for UI/UX developers rather than more parachain APIs. For example, a UI should be able to connect to a single API instance and make queries like:

// Account balances: Returns the balance of an account on multiple chains.
// Would allow UI to display e.g. total balance on an account of an asset
// in the entire network.
accounts.balance(account, token) => [(chainId, balance)] where:
  token: enum = {
    Parent, // Relay Chain token
    Para(Id), // Native token of parachain `Id`
    Asset(Id), // Asset `Id` registered on Statemint/e
  }
  chainId = ParaId (or Parent for Relay Chain)
  balance = balance on the ParaId of the tuple

// Returns any identity info from chains (e.g. from Relay Chain's Identity
// pallet or KILT) such that a UI could render that instead of an
// address/0x1234...
accounts.identity(account) => [IdentityInfio]

// Return an array of `Role`s that an account fulfils in the network. Could be
// e.g. a nominator on the Relay Chain, a collator on a parachain, a Councillor
// on a governance chain, etc.
accounts.roles(account) => [Role]

Likewise, a follow on step to this could be transaction construction/routing logic, so that a UI/UX developer can use a simple API like tx.assetTransfer(asset: Id, to: Account, amount: Balance) and the middleware would find the appropriate chain (e.g. Statemint) and construct the transaction with the account's nonce on that chain as well as route the signed transaction to the appropriate node.

TLDR: Provide an API on the model of Polkadot/Kusama as single networks rather than a bunch of APIs of disparate chains.

Hi Joe, thank you for the suggestion! We certainly see a lot of value in creating a unified API that serves all networks on Polkadot and Kusama, and we have included it as one of the top priorities on our roadmap. We're working towards our main launch currently and we believe that a functional dashboard with helpful usage metrics, project and team management functionality will be critical for dApp developers in their early stages. This is the progression we're working towards: 1) We will start with unifying the endpoints for users under user unique ID, so they can switch between networks by plugging in different network names 2) Run nodes to support all live parachain networks on Polkadot and Kusama 3) Subsequently, we'll work on developing our own API gateway to enable the suggested 'all-in-one' API solution We will be in touch once we have our portal up and stable. Thank you once again for your constructive feedback. Eric Poh - Pinknode