Consolidate duplicated infrastructure content in dapp-share.mdx
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with embedded-wallets/sdk/ios/advanced/dapp-share.mdx and compare its duplicated sections with the linked Embedded Wallets infrastructure page. Condense the infrastructure and mobile user-experience explanations, then remove the repeated dapp share definition. Done means the page preserves the key mobile backup rationale without duplicating existing documentation.
Written by the indexing model from the issue text.
Description
Problem
embedded-wallets/sdk/ios/advanced/dapp-share.mdx duplicates content from the Embedded Wallets infrastructure page across two sections:
- "Embedded Wallets infrastructure at a glance" (lines 7-28) reproduces the share-splitting explanation (ShareA, ShareB, ShareC, 2-of-3 reconstruction) that already lives on the infrastructure page.
- "Dapp share in iOS" (lines 49-53) repeats the dapp share definition nearly verbatim from the end of the "Mobile platform user experience" section (lines 45-47).
The "Mobile platform user experience" section (lines 30-47) is also largely background explanation that could be condensed.
Suggested fix
- Replace the "Embedded Wallets infrastructure at a glance" section with a 1-2 sentence summary and a link to the infrastructure page.
- Condense "Mobile platform user experience" to 2-3 sentences covering the key point: on mobile, browser storage is unreliable because users may unknowingly clear it, so a dapp share provides a backup.
- Remove the duplicated definition in "Dapp share in iOS" (lines 51-53) since it repeats lines 45-47.
Files affected
embedded-wallets/sdk/ios/advanced/dapp-share.mdx
- Dominant language
- MDX
- Stars
- 861
- Forks
- 2.1k
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 10
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.
More from MetaMask/metamask-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
MetaMask/metamask-docs#2928 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
MetaMask/metamask-docs#2895 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
MetaMask/metamask-docs#2894 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 5/100
MetaMask/metamask-docs#3050 · 1 comment ·
-
Server-wallet signing fails with "signing job failed" on all chains — mm CLI setup fully verified Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
MetaMask/metamask-docs#3032 ·
All issues in MetaMask/metamask-docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100