MetaMask / MetaMask/metamask-mobile
Best practices documentation for devs
Open
Nobody has claimed this yet.
contributor experience
devrel
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### **Description**
- Provide more documentation from a dev perspective
### **References**
- [Old ticket](https://github.com/MetaMask/metamask-mobile/issues/340)
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 by reviewing the linked old ticket (#340) and the repository’s existing developer documentation. Define which best practices need coverage and where they belong; the issue does not specify files, tests, or a completion boundary.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100