Bug 510394

SUMMARY

The current star rating system in Discover is composed of 5 stars, which are "shaded" or "coloured-in" to visualise the average rating of an application. Suggestion is to replace this entirely with an average rating expressed in decimal form.

STEPS TO REPRODUCE
1. Open Discover
2. Click all applications
3. Sort by rating

OBSERVED RESULT

You are presented with a visual star rating system, with the total number of reviews written next to it for each app in the list. This presents several problems, in that the "shading" of the stars is not entirely accurate, and even if it was, it is very difficult to see at a glance whether or not an app has, for example, a rating of 2.9/5 or 2.8/5.

EXPECTED RESULT

The average rating is clear and easy to compare with other apps in the list.

SOFTWARE/OS VERSIONS

Operating System: KDE Linux 2025-09-20
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Pentium® 3805U @ 1.90GHz
Memory: 4 GiB of RAM (3.7 GiB usable)
Graphics Processor: Intel® HD Graphics
Manufacturer: LENOVO
Product Name: 80EW
System Version: Lenovo B50-80

ADDITIONAL INFORMATION

The 5-star rating system in its current form is a bit difficult to deal with. Replacing it with a purely decimal system offers these benefits;

--- Reduced code complexity. Average rating expressed as a decimal is very simple maths, find the average and round the answer to one decimal place. Easier to write & read code, easier to troubleshoot, easier to maintain codebase etc etc.
--- Precise information. "Three point eight stars out of five" is expressed as 3.8/5. This is borderline impossible to misunderstand, misread or misinterpret, unlike the graphical representation currently used.
--- Easy to compare. A list containing 3 apps showing 4.8/5, 4.9/5 and 5/5 is simple to read, understand and compare.
--- Fewer bug reports. There are far fewer graphical glitches to be experienced with a decimal system.

I will attach screenshots showing examples of such behaviour.

Original bug report >>> https://bugs.kde.org/show_bug.cgi?id=423292