-
-
Notifications
You must be signed in to change notification settings - Fork 326
Description
I have already checked through the existing bug reports and found no duplicates
- Yes
App Version
1.4.2
Music Server and Version
Navidrome 0.6
What local environments are you seeing the problem on?
Desktop macOS
What happened?
When browsing large playlists in Feishin, there's a frustrating UX issue where the display order of the playlist directly affects how search results are ranked, creating an impossible choice between two conflicting needs.
Steps to reproduce
Current Behavior
Default playlist display order (oldest to newest)
Shows the same first 50 songs repeatedly
Makes it hard to discover recently added tracks
Large playlists become hard to navigate
Reversed playlist order (newest to oldest)
Solves the discovery problem
Shows recently added tracks at the top ✓
But: When searching within the playlist, the best match (the song you're looking for) appears last instead of first ✗
The core issue: The playlist sort order is directly coupled with the search result ranking, forcing users to choose between usable browsing or usable search.
Expected Behavior
Playlist display order should default to: newest to oldest
This is the standard pattern on Spotify, Apple Music, etc.
Users expect to see recent additions first
Search within playlists should:
Rank results by relevance (best match first)
Be completely independent from the playlist display order
Always show the most relevant result at the top, regardless of how the playlist is sorted
Why This Matters
Large playlists become unusable:
You're forced to scroll through hundreds of songs to find anything new
Standard UX expectation: Every major music service shows recent additions first
Search should be about relevance, not sort order: These are two separate concerns and shouldn't interfere with each other
Possible Solutions
Option 1: Change default sort order + decouple from search
Switch default playlist order to descending (newest first)
Make search results always rank by relevance, ignoring playlist sort
Option 2: Add a separate "search ranking" setting
Keep current playlist sort options
Add an independent toggle for search result ranking
Option 3: Intelligently handle both concerns
Default to descending order
Detect search context and always prioritize relevance in search results