MetaMask / MetaMask/metamask-extension
UX extremly confusing in last updates... e.g cannot see which accounts has sepolia ether
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
Every update of MetaMask seems, at least for me, less intuitive than the last one.
A lot of people are migrating to Rabbit, and I think this might be the reason.
I can’t see the “See on Etherscan” button anymore.
Accounts don’t show the Ether balance on the selected networks.
Selecting networks is extremely confusing since it has to be done inside an account.
Since there's no exchange rate for testnet Ether you just see “No conversion rate available” message and an extremely small value.
i don't even see the address on the main page of the account...
NGL i understand that you are trying to on board users, but could you put a "dev" mode with all things i said that were always present?
### Scenario
_No response_
### Design
_No response_
### Technical Details
metamask_version=13.7.0
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reproducing the reported account, network-selection, balance, address, and Etherscan visibility concerns in MetaMask 13.7.0; a complete issue would need a defined dev-mode scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100