Be consistent with the supported-platforms images/badges/logos

[LucasDondo]

Describe your request

The Browser Add-Ons section has badges for both Firefox and Chromium-based browsers, but the KDE Connect section has only text-based URLs.

Proposed solution

The evident solution is to add the badges for each platform mentioned in the KDE Connect section. I actually started working in a PR that does exactly that (following the scheme used in the Browser Add-Ons section).

However, the only problem is that OpenRepos has no official badge. So I though maybe I could use SailfishOS' one. But they have no badge either.

Alternatives

The alternatives I thought in order to achieve the maximum possible consistency:

• Badges option: Use badges for everything except for Sailfish OS, in which case we can use the Sailfish OS logo.
• Logos option: Use the logos of each supported OS and browser (using Chromium's logo for the Chrome Web Store). In Android's case, a pop-up could appear when clicking on it, with both Play Store and F-Droid's logos to choose from.

Badges option	Logos option
Slightly less consistent, but more meaningful	Overall more consistent, but Chromium's logo might be meaningless for some users

GSConnect version

66

Installed from

GitHub's repository (not GitHub releases).

GNOME Shell version

48

Linux distribution/release

Ubuntu 25.04

Additional context

[ferdnyc]

Additional alternatives

• Do nothing. Web stores have badges, other types of distribution system may or may not (but certainly, not all do), so the current design is pretty much as expected.

Before going any further down this road, I feel a discussion is warranted as to why that's not an option (I feel it is) or what the down sides are to sticking with the current layout.

Side point

There's also the unrelated issue that our Chrome Web Store badge is currently not really useful, as Chrome's blocking of manifest v2 extensions is now in full, un-overridable force. So until the extension gets an update, that badge links to effectively nothing.

[ferdnyc]

Huh... you know, something I never thought about: How do the badges get localized?

I'm beginning to suspect they don't. Which is a real concern, IMHO. Presumably they COULD (If there are SVGs for translated versions of the badge content in other languages, and we were to bundle all of those into the extension), but as things currently stand I expect we're showing users "Get the ADD-ON" and "Available in the Chrome Web Store" messages no matter what the interface language is set to. That's not great.

[ferdnyc]

In Android's case, a pop-up could appear when clicking on it, with both Play Store and F-Droid's logos to choose from.

...If (theoretically) we have Play Store and F-Droid logos, why do we need the pop-up? IOW, why couldn't both of those just be at the top level, instead of the Android logo? (Or both paired with the Android logo, if we're concerned — and I AM — that the store logo alone won't be sufficiently meaningful to people.)

[ferdnyc]

IIRC, long ago the interface did use the Play Store and F-Droid badges. (Still viewable in the wiki.) The links were changed to text when Sailfish was added, for the reasons you've discovered, so that at least that section was consistent.

Whether inconsistency between the sections is a problem serious enough that it warrants forcing some sort of graphical representation for each app store link... is the question.

(Heck, another alternative: we could drop the badges, and use text links for the extensions as well. That would also be consistent, if consistency is paramount. And the links would be localizable!)

[LucasDondo]

what the down sides are to sticking with the current layout

The technical answer would be: consistency across related sections. But, TBH, the core reason I raised this issue (and I'm willing to create the PR) is I believe it would not only look better, but also make it easier for people to, at first sight, get a glimpse of the supported platforms they might like using GSConnect with (you know, since the already-familiar and recognizable colors and icons).

I'll represent this way of viewing the problem as colorful in the table below.

---

You're right Frank, the other option would be to move everything to text. So, to recap:

Alternative	Consistency	Localization	Colorful
Use OS/Browser logos	Excellent	Not a problem	Yes
Use per-store text	Excellent	Not a problem	No
Use per-store badges	Broken (since OpenRepos has no badge)	Possibly solvable, but problematic	Yes

The one problem I do see with the logos alternative is: what to do with the Chrome Web Store logo? Use Chrome's logo? But Chromium is more universal. But Chromium's logo is not as known as Chrome's. Or should we just remove it since it doesn't work anyways?