MetaMask / MetaMask/metamask-mobile
Why do you block the back button
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
**Describe the usability problem**
_A clear and concise description of the specific usability issue_
You block the back button in the Android app, why? Usually this is a really bad decision.
**Screenshots**
_If applicable, add screenshots or links to help explain the issue_
**Expected behavior**
Don't block the back button at any time
------------------------------------------------------------------------------------------------------
_filled out after submission_
**User impact | Usage frequency | Feasibility scores**
_How important is this to the user, what the user wants to accomplish | Daily, weekly, monthly | Small, medium, large_
Contributor guide
Research direction
Start by reproducing the blocked back-button behavior in the Android app and identify which screen or navigation path causes it. Done means the Android back button is not blocked anywhere, with the behavior verified across the affected flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100