Open maaikevanleuken opened 4 months ago
So you mean you can hide certain columns to fit the overview better on a smaller screen size without too much scrolling?
Not to hide the columns, but the rows. e.g. filter out all rows (wallets+agents+interop profiles), such that I only see wallets. It will become less long vertically. We can also opt that for e.g. interop profiles, many columns are not relevant, and dynamically remove them when the user filters on them. Would require some implementation work though. Let's first try out filtering on the rows.
Ah, got it. Right now it's possible to filter for the wallet type (edge or cloud).
How do we separate wallets from agents? For some people in the SSI space, it's the same. For others a wallet is only the storage component and the agent the implemented logic to handle it.
Is it better to separate like "capable to handle natural persons/natural persons". So if a wallet/agent has none of those, it it for example only capable for iot devices? I think we need more clarification here about the purpose of each filter.
holderCapability = true
issuerCapability = true OR verifierCapability = true
ebsi = true
urlAppStore != '' OR urlGooglePlayStore != ''
organisationalWallet = true
I'm referring to the characteristics in the main branch's flattened_wallets.json", but I think you could build the same filters in the
next` version.
Add filters to the overview, to keep it uncluttered.
These filters could be: