QuantumBadger / QuantumBadger/RedReader
BUG (?) "Back" behavior from Inbox after opening from notification
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
When RR notifies user of a new message in their inbox, and the user starts RR via that notification, once they've read the message and want to do something other than directly reply to said message (e.g. look for one of their own comments for reference), the back button exits RR instead of going back to the main interface as one might expect (causing them to have to go find RR on their phone and start it again the long way). If this is intended behavior, then I'd like to at least request an option that it not do so, but instead always go back to the main screen before actually exiting.
Thank you very much both for this very useful app, and for taking the time to read and consider this issue.
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
No files, tests, or entry points are named. Reproduce the notification-launched Inbox flow and inspect how Android back navigation handles the message screen; clarify whether Back should reach the main interface before exit. Done means the chosen behavior is implemented and verified for that flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100