Right now the "process" is basically me or someone else saying, "hey, the apps in here are kind of stale; let's improve this a bit." I think it should be made more programmatic. See https://bugs.kde.org/show_bug.cgi?id=389509

The following opinions/suggestions are to be aligned with "What Discover Is" and "What Discover Isn't" at Discover Page.

I agree there is a lack of better searchable/filterable information of apps and this improvement type will have a much higher value than a new GUI and also benefit the community by lowering the dependency and overheads of a writing maintenance team.

As @ngraham mentioned on Bug ID 389509, adding a "Category" will not be solving the actual problem short or long term.

An approach may be to get the community/users involved in the process to validate information. Some are already providing reviews which is a step in a good direction.

From my personal usage over the past 3 months using Kubuntu for the first time I would have had a much more pleasant experience if I was able to perform/rely on the following capabilities. Capabilities which will then support improving the Search/Filter functionality:

1. Up-vote/Down-vote a review. (Improve quality of reviews and support future functionality to award reviewers)
2. Up-vote/Down-vote metadata information. (Improve quality of product information supporting user decision making and lower frustration)
3. Report "Update Request" which inform the dev group, maintainer, and also provide the user an opportunity to provide the updated information. (Allow the community to support the goals of the Discover product)

Methods to support the community to support this product:

1. Provide a template of good metadata to developers have a higher rate of doing it right the first time. @ngraham already covered a good part of this in the Bug ID 389509 post.
2. In the "About" add more information such as a link to this Phabricator, the bugs.kde.org, the link to Discover product page (https://userbase.kde.org/Discover) , IRC, and to a wiki that will help new developers. This can improve visibility and improved user experience to feel more connected with the product.

Discover already allows you to upvote/downvote reviews FWIW.

Upvoting/downvoting metadata information I'm not sure is that useful, because in the end someone still needs to go and improve it. What might be better is displaying a link to where the metadata can be viewed and edited or something.

I'm open to technically feasible suggestions for how to get more people involved in improving appstream information. I tried my hand at this and found it pretty exhausting to do alone. A lot of 3rd-party developers seemingly don't care about this or are actively hostile to improvements in their apps' metadata. It was quite disheartening TBH.