QuantumBadger / QuantumBadger/RedReader
No arrow button to return to a page volountarly/accidentally left
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
Hi,
How to reproduce:
Click on a subreddit->click on a thread->press the return arrow at the bottom of the phone=there is no way to return to the thread unless you click on it again.
Same thing if from a subreddit I return to RR "homepage", no way to return to the subreddit or the thread.
Give the limitations of access to Reddit, maybe not having a "->" button is a design choice in order to avoid excessive accesses, but I wasn't sure so I decided to ask if you could implement it.
Edit: I just saw that in the googleplay reviews one review from August 4th with 3 upvotes asks for something similar, so maybe I am not the only one who accidentally leaves a thread :) :)
"Excellent app for browsing Reddit. Only change I'd like to see is a confirmation when clicking "back" from a subreddit so that you don't inadvertantly lose your position where you've scrolled down to. Otherwise, love how customisable it is in terms of theme and cache management is quite extensive"
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 tracing the Android navigation between the subreddit, thread, and RedReader homepage screens. Reproduce the phone back-button flow described in the issue and determine how returning to a previously visited page should work, including the requested return path and any retained scroll position. Done means users can recover the subreddit or thread they accidentally left without reopening it manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100