Search results are sorted alphabetically by package name, which buries the most relevant matches. Searching "spotify" shows "alsotropon" near the top because it comes first alphabetically, while the actual spotify package is far down the list.
We should score results by relevance — exact name match first, then name prefix, name substring, and finally description-only matches. Within each tier, secondary sort could use AUR popularity or alphabetical order.
This affects both sync and AUR search results independently of the AUR integration work.
Search results are sorted alphabetically by package name, which buries the most relevant matches. Searching "spotify" shows "alsotropon" near the top because it comes first alphabetically, while the actual spotify package is far down the list.
We should score results by relevance — exact name match first, then name prefix, name substring, and finally description-only matches. Within each tier, secondary sort could use AUR popularity or alphabetical order.
This affects both sync and AUR search results independently of the AUR integration work.