maxrave-dev / maxrave-dev/SimpMusic

[UX] Focus search input and open keyboard when tapping Search button again

Open
#2,324 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
11.4k
Forks
599
Avg merge
3d 18h
Merged PRs (30d)
7

Description

Problem Description

On larger modern devices, reaching the top of the screen to tap the search bar requires awkward thumb stretching during one-handed use. After tapping the bottom/navigation Search button to go to the search page, the user is still forced to manually reach up to tap the text input to begin typing, which adds unnecessary interaction friction.

Proposed Solution

Implement a double-tap / re-tap shortcut for the Search navigation button:

First Tap: Navigates to the Search page (normal behavior).

Second Tap (when already on the Search page): Automatically focuses the search input field and displays the soft keyboard.

This allows users to start typing immediately without having to stretch their fingers to touch the search input at the top of the screen.

Alternative Solutions

Auto-focus on navigation: Automatically focus the search bar and bring up the keyboard immediately upon opening the Search page (though this might be intrusive if a user just wants to browse the tiles).

Bottom Search Bar: Place the search text field at the bottom of the screen instead of the top.

Additional Context

UX Inspiration: This interaction pattern is commonly used in apps like the Google Play Store, where tapping the active Search tab button again focuses the search bar and activates the keyboard for improved reachability and faster search workflows.

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

Start by locating the Search navigation button, Search page, and search input entry points, then trace how repeated navigation taps are handled. Verify the existing first-tap behavior before adding the re-tap interaction. Done means tapping Search again while already on the Search page focuses the input and displays the soft keyboard without changing the normal navigation behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.