Option to place the app drawer search bar at the bottom of the screen
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by reading the app drawer layout and its existing search and keyboard settings to find where the search bar and app list are arranged. Add a top or bottom position setting that places the bar above the navigation area when selected, and check that it works with automatic keyboard display. Done when either position is selectable and the app list remains usable in both configurations.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Add a setting to move the app drawer search bar from the top to the bottom of the screen, just above the navigation bar, with the app list above it.
Why do you want this feature?
On modern tall phones, the top of the screen is the hardest area to reach with one hand. My workflow is: swipe up from the home screen to open the drawer and look for the app. If it isn't visible right away, I tap the search bar and type. Right now that bar is at the very top, so I have to change my grip or use my other hand every time.
The current workaround, "show keyboard automatically", avoids the reach problem, but the keyboard then covers about half of the app list every time I open the drawer, even when the app I want is already visible and I don't need to search.
With the search bar at the bottom, the drawer would open showing the full list with no keyboard, and the search bar would be right under the thumb when needed. This is the same reachability idea used by many modern launchers and by Chrome and Firefox with their bottom toolbars.
A simple toggle such as "Search bar position: Top / Bottom" would be enough, and it should work well together with the existing keyboard option.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Launcher#456 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Launcher
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
saisaharsh3/Leftovers#13 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
navikt/esyfo-narmesteleder#700 ·
Maintainers usually reply within 1 day
-
A2A agent card served at agent.json, but A2A 0.3.0 uses agent-card.jsonPossibly taken @hadirsa claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
embabel/embabel-agent#2142 ·
Maintainers usually reply within 1 day
-
bug feedback required
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
streetcomplete/StreetComplete#7275 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Kotlin/kotlin-lsp#288 ·