Erik Nilsson

Update README.md

1

Made your README.md up-do-date and did some structuring to the information hierarchy.

Update design-guidelines.md

7

Minor snaps design guidelines update

Action within input field

2

Let's introduce an (optional) action on the right-end of the input field (with the same available states as for any action) 

Custom footer component

1

Let's [introduce](https://www.figma.com/file/a96Mb76VZDNYPMcOXaLX92/Components?type=design&node-id=270%3A10866&mode=design&t=pNUpDEUUTGNELIM9-1) our footer surface via the footer component with these initial states.

Abstract system-level permissions

5

Some of our permissions might be too low-level for users to see during the installation phase. Two things: - Potentially introduce another weight (5) to group these implicit permissions -...

Address component

2

Let's introduce a component to parse any arbitrary account address so it can be displayed in a variety of ways depending on the props. E.g. "Gaming Account 1" or the...

Let's introduce a permission so snaps can see all assets (tokens, NFTs, etc) including metadata for all available accounts. To be used in any custom UI surface.

Let's look into some way to let snaps consume metadata (name, address, avatar, balance, etc) for all available accounts so they smoothly can populate them in custom UI in any...

Introduce loading states to our custom UI buttons

1

Let's add a loading state to our; 1. [Button component](https://www.figma.com/design/gHWl7G8ih3YXesly2XaA0R/Snaps-DS?node-id=17-463&t=YDinFWD7OZ7mLQT7-1) within the container 2. [Button component](https://www.figma.com/design/gHWl7G8ih3YXesly2XaA0R/Snaps-DS?node-id=75-813&t=YDinFWD7OZ7mLQT7-1) in the footer