Mobile feature parity

Open
#3,583 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
mobile

Research direction

The issue body names no files, tests, entry points, or specific mobile capability. Start by identifying the mobile features that need parity and the relevant TypeScript areas, then define the expected behavior and tests before implementation.

Written by the indexing model from the issue text.

Description

Epic snaps-feature snaps-refined-backlog

This issue has no description.

Dominant language
TypeScript
Stars
853
Forks
662
Avg merge
2d 8h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/snaps

All issues in MetaMask/snaps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.