MetaMask / MetaMask/metamask-extension
Extension:UX Improvement:Consistent list interaction
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?
See also [Draft proposal Account sorting, filtering, grouping](https://docs.google.com/document/d/18DPze8mIc0M5pTKitffmyhHncAZeTKWst9_b0k4WvmQ/edit?usp=sharing).
On Extension we recently introduced ordering of accounts. The foreseen implementation was to allow drag and drop. During implementation issues were encountered with drag and drop and existing account grouping. `Pinning` was implemented instead. On the Network list, drag and drop is available.
We want to identify and propose a general interaction pattern for list ordering that can be applied to Mobile, Extension and different lists on both platforms.
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### 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
Start with the linked proposal on account sorting, filtering, and grouping, then compare the existing Extension account list with the Network list's drag-and-drop interaction. Define a general ordering pattern that addresses pinning, grouping, and drag-and-drop across Mobile and Extension lists. Done requires an agreed design and documented acceptance criteria, which this issue currently lacks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100