TeamAmaze / TeamAmaze/AmazeFileManager
New app selector has broken last app / default app selection and wastes screen space
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
Old behavior of the app selector
In 3.3.2 (IIRC), when I tapped on a file, an
app selector would pop up that had 3
important features:
• It would remember my last selected app,
so I only needed to press "Just once" or
the appropriate app icon.
• By selecting an app once, then opening
the file again, but this time tapping on
"Always", I could select the default app
for the current file type, so the app selector
would never appear again, and the
appropriate file type would automatically
be opened by the selected default app.
• It showed quite a few apps at once. Maybe
in side-scrollable/swipeable panels with
8 apps per panel, if it was my Android 9
system's app selector that Amaze used.
New behavior of the app selector
(Versions >= 3.5.0, maybe earlier)
• It will not remember my last selected app
• I cannot select the default app, as the app
selector does not remember my last
selected app
• It shows only 4 apps at once
To Reproduce
Steps to reproduce the behavior:
- Tap on a file name to open the file.
- Observe the new app selector popping up.
- Depending on your temper, curse and/or face-palm. ;)
Expected behavior
Just let Amaze use the Android system's app
selector.
If you want to replace it, replace it by
something better, maybe:
• show as many apps at once as screen space permits
• have an icon switching between grid and
list mode (and remember this setting)
• have an icon sorting the grid/list of apps
alphabetically or by the time they were last
used (and remember this setting)
Screenshots
(Trying to provide screenshots later)
Smartphone (please complete the following information):
- Device: Huawei Mate 20
- OS: Android 9
- Rooted: No
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 app-selector flow reached when tapping a file name and compare it with the Android system selector behavior described in the issue. Done means the selector can remember the last app, support selecting a default app, and use screen space more effectively without recurring unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100