MetaMask / MetaMask/SIPs

SIP For Auto Pulling UI for Snap

Open
#135 3 comments 0 reactions 0 assignees View on GitHub
snaps-deferred
Dominant language
HTML
Stars
42
Forks
19
PR merge metrics
No merged PRs in 30d

Description

There are a few ways to go about this but the ultimate goal of this SIP is to improve a Snap users UX. Right now the least clicks/flow to get to a Snap UI is the following:

Step 1.
![Step 1](https://github.com/MetaMask/SIPs/assets/41382129/3ac4c47c-3c71-4d4c-953b-e9d358323f90)
Step 2.
![Step 2](https://github.com/MetaMask/SIPs/assets/41382129/e1b8750b-796b-45f2-9b8d-bdbe201901a5)
Step 3.
![Snap 3](https://github.com/MetaMask/SIPs/assets/41382129/665e1798-f8d3-4604-b49b-7709561be70f)
Step 4.
![Step 4](https://github.com/MetaMask/SIPs/assets/41382129/94c2a94f-a301-4645-92b5-35652353e0d3)

I propose the ability to either auto detect you are connected to a snap and on the initial load of the extension (when you click the extension icon to open), the Snap UI page is displayed.

If this is more of a drag or development haul the second best option would be where you see the dApp connected Icon (step 1 image), when you click on it, it automatically pulls up the Home Page/settings for that Snap.

Looking forward to thoughts!

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by reviewing the current Snap connection and extension-opening flow, then determine which proposed behavior is selected. Done means a connected Snap user reaches its UI automatically from extension load or the dApp-connected icon with fewer steps.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.