Checklist
Feature Description
Feature Request: Generic "Find in Current Screen" Function Similar to Android Browsers
Description
I would like to suggest a generic "Find" function similar to the "Find in Page" feature available in Android web browsers.
Instead of creating separate search functions for individual screens, the app could provide a reusable Find action that searches the text content available on the currently opened screen.
Basic workflow:
- Open any screen containing a list or text content.
- Open the three-dot menu (⋮).
- Tap Find.
- Type text.
- Matching items on the current screen are highlighted or filtered.
This is not intended to replace the existing service search. It would act as a local screen-level search tool.
Inspiration
The inspiration comes directly from Android web browsers.
Most Android browsers provide a "Find in Page" function.
When a webpage contains a large amount of text, users can open the browser menu, tap Find in Page, and instantly locate matching text without manually scrolling through everything.
I originally started using this workflow while managing large playlist collections.
Example:
- Open YouTube in an Android browser.
- Choose Add to Playlist.
- A long list of playlists appears.
- Instead of manually scrolling through dozens or hundreds of playlists, use Find in Page.
- Type part of the playlist name.
- The browser immediately jumps to the matching playlist.
Over time I realized that the same concept could be useful inside the app itself.
What Should Be Searchable?
The idea is similar to a browser's "Find in Page" feature.
If a user can normally see and read text on the current screen, that text should be searchable through the Find function.
Examples may include:
- Playlist titles
- Video titles
- Channel names
- Download names
- History entries
- Subscription names
- Bookmark names
- Other visible text-based items
The intention is not to search hidden application data, internal identifiers, or implementation details.
From a user's perspective, it simply searches the text content presented by the current interface.
Example Use Cases
Playlists
A user has many playlists.
Instead of scrolling through the entire list, they can use Find and type part of the playlist name.
History
A user remembers part of a title but has hundreds or thousands of history entries.
Using Find would make locating it much easier.
Downloads
A user wants to locate a specific downloaded item without scrolling through the entire list.
Subscriptions
A user follows many channels and wants to quickly find one.
Future Screens
Any future screen containing large amounts of text or lists could potentially benefit from the same Find functionality.
Why A Generic Find Function?
Without a generic Find function, individual screens may eventually require their own separate search implementations.
A reusable Find action could provide a consistent experience throughout the app.
Instead of:
- Playlist Search
- History Search
- Downloads Search
- Subscription Search
- Bookmark Search
Users would simply learn:
Menu → Find
and use the same workflow everywhere.
Benefits
Reduced Scrolling
Large collections become easier to navigate.
Familiar User Experience
Many users already understand browser-style "Find in Page" behavior.
Reusable Design
A single feature can work across multiple screens.
Local and Fast
Most searchable information already exists locally inside the app.
Future Scalability
New screens could automatically benefit from the same Find functionality.
Related Discussions
Related issues discussing search or filtering in specific areas:
Those requests focus on particular search use cases.
This request is different because it proposes a reusable "Find in Current Screen" function inspired by Android browsers' "Find in Page" behavior.
Why This Feature Would Help
As users accumulate more playlists, subscriptions, downloads, bookmarks, and history entries, scrolling becomes less efficient.
A browser-style Find function would provide a familiar, lightweight, and scalable way to quickly locate information already visible within the currently opened screen.
Checklist
Feature Description
Feature Request: Generic "Find in Current Screen" Function Similar to Android Browsers
Description
I would like to suggest a generic "Find" function similar to the "Find in Page" feature available in Android web browsers.
Instead of creating separate search functions for individual screens, the app could provide a reusable Find action that searches the text content available on the currently opened screen.
Basic workflow:
This is not intended to replace the existing service search. It would act as a local screen-level search tool.
Inspiration
The inspiration comes directly from Android web browsers.
Most Android browsers provide a "Find in Page" function.
When a webpage contains a large amount of text, users can open the browser menu, tap Find in Page, and instantly locate matching text without manually scrolling through everything.
I originally started using this workflow while managing large playlist collections.
Example:
Over time I realized that the same concept could be useful inside the app itself.
What Should Be Searchable?
The idea is similar to a browser's "Find in Page" feature.
If a user can normally see and read text on the current screen, that text should be searchable through the Find function.
Examples may include:
The intention is not to search hidden application data, internal identifiers, or implementation details.
From a user's perspective, it simply searches the text content presented by the current interface.
Example Use Cases
Playlists
A user has many playlists.
Instead of scrolling through the entire list, they can use Find and type part of the playlist name.
History
A user remembers part of a title but has hundreds or thousands of history entries.
Using Find would make locating it much easier.
Downloads
A user wants to locate a specific downloaded item without scrolling through the entire list.
Subscriptions
A user follows many channels and wants to quickly find one.
Future Screens
Any future screen containing large amounts of text or lists could potentially benefit from the same Find functionality.
Why A Generic Find Function?
Without a generic Find function, individual screens may eventually require their own separate search implementations.
A reusable Find action could provide a consistent experience throughout the app.
Instead of:
Users would simply learn:
Menu → Find
and use the same workflow everywhere.
Benefits
Reduced Scrolling
Large collections become easier to navigate.
Familiar User Experience
Many users already understand browser-style "Find in Page" behavior.
Reusable Design
A single feature can work across multiple screens.
Local and Fast
Most searchable information already exists locally inside the app.
Future Scalability
New screens could automatically benefit from the same Find functionality.
Related Discussions
Related issues discussing search or filtering in specific areas:
Those requests focus on particular search use cases.
This request is different because it proposes a reusable "Find in Current Screen" function inspired by Android browsers' "Find in Page" behavior.
Why This Feature Would Help
As users accumulate more playlists, subscriptions, downloads, bookmarks, and history entries, scrolling becomes less efficient.
A browser-style Find function would provide a familiar, lightweight, and scalable way to quickly locate information already visible within the currently opened screen.