Bug 387805

Summary:	Multiple additional sort options based on popularity, ratings, and quality
Product:	[Applications] Discover	Reporter:	Nate Graham <nate>
Component:	discover	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	mutlaqja
Priority:	NOR
Version First Reported In:	5.11.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:	383518
Bug Blocks:

Description Nate Graham 2017-12-11 19:50:49 UTC

This idea got a positive reception in the discover-design Telegram room, so I thought I'd promote it to a feature request.

When browsing and searching, KDE discover should have additional sort options designed to delight different types of people:

1. Recommended (for people who trust experts)
2. Most popular (current default; for people who believe in the wisdom of crowds)
3. Overlooked gems (high rated but infrequently downloaded; for people who like to discover hidden value)
4. Controversial (ratings are all over the map; for people who like to argue)
5. Alphabetical (for people who want "Just The Facts Ma'am" without any filtering of the data)

The last-used view should be remembered across app launches.


Discover's Current UX implements rough versions of #1 (on the home screen, in a limited form) and #2 (the browse lists, though the order isn't made clear). With this, we could actually get rid of the Home screen entirely and have Discover open to an app list with a sort order determined by a visible UI control like a dropdown menu or something.

Comment 1 Nate Graham 2017-12-12 14:19:34 UTC

*** Bug 387378 has been marked as a duplicate of this bug. ***

Comment 2 Jasem Mutlaq 2018-01-14 05:11:41 UTC

Lovely idea. I presume #1 is the same thing as "Editors Pick", correct?

Comment 3 Nate Graham 2018-01-14 05:17:57 UTC

Yes, exactly. That would basically be the current contents of the Home screen (which I am hoping to rename to "Featured Apps": https://phabricator.kde.org/D9868)

Comment 4 Aleix Pol 2018-01-25 13:14:42 UTC


*** This bug has been marked as a duplicate of bug 383518 ***