TeamAmaze / TeamAmaze/AmazeFileManager

Remove pull-to-refresh gesture to reduce battery consumption

Open
#4,034 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

While my experience with Amaze File Manager is largely satisfactory, it has a common problem: the pull-to-refresh gesture.

Pull-to-refresh is one of those things that seem useful in theory. In practice, it turns out to be a burden.

Pull-to-refresh is an annoyance which causes unwanted refreshes while scrolling up. Each unwanted refresh needlessly wastes battery charge.

Pull-to-refresh forces users to scroll up slowly and carefully to avoid accidentally refreshing. Pull-to-refresh denies the ability to pull down for verifying whether the top of the list is being viewed. Pull-to-refresh takes more control away from the user than it gives the user.

Refreshing is rarely ever needed in a file manager, and at the occasion where it really is necessary, it would take half a second to access it from a submenu.

Pull-to-refresh is implemented into apps only due to being a "design trend", not due to its actual usefulness.

Pull-to-refresh is a burden in web browsers, and no less inside other apps.

Moving down the finger should not be an ambiguous gesture. It should do exactly one thing: move up the page.

I never want to see that annoying circle with the refresh icon on my screen ever again. Apologies for the impoliteness, but pull-to-refresh really got on my nerves. I would love to see this design trend end. Pull-to-refresh is implemented without considering its actual usefulness, only because it is a design trend.

Please remove the pull-to-refresh gesture. Thank you for your consideration.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Search the Android/Kotlin UI for the pull-to-refresh implementation and first confirm which file-manager screens use it. Done means the gesture and refresh indicator are removed while ordinary scrolling still works, with relevant UI tests or manual verification run if available.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
frontend, mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.