Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the branding document for JS apps #113

Open
Jaifroid opened this issue Nov 13, 2024 · 8 comments
Open

Update the branding document for JS apps #113

Jaifroid opened this issue Nov 13, 2024 · 8 comments

Comments

@Jaifroid
Copy link
Member

@rgaudin I noticed your discussion of branding elsewhere (e.g. on Kiwix Desktop). I was not aware there was a branding document, and no-one has ever mentioned it to me!

It needs updating as far as the JavaScript apps are concerned.

  1. Remove the entry for "Kiwix UWP", and the repo it points to, which no longer exists (the Repo name was changed to kiwix-js-pwa a couple of years ago).
  2. We need an entry for "Kiwix PWA", pointing to https://github.com/kiwix/kiwix-js-pwa.
  3. We need an entry for "Kiwix Electron", also pointing to https://github.com/kiwix/kiwix-js-pwa.

On the custom apps made with Electron for Linux and Windows ("Wikivoyage by Kiwix" and "WikiMed by Kiwix"), I consulted about the branding before I started publishing them (in the Microsoft Store and on GH Releases) around 6 years ago. It was suggested I use the formula "by Kiwix" in the title of the apps. You can see their branding in the MS Store here:

https://apps.microsoft.com/detail/9phjsnp1cz8j
https://apps.microsoft.com/detail/9n5sb90q4jbj

This can't easily be changed now, at least not without unpublishing the apps, and trying to move all users to a new app, which would inevitably disrupt and strand users.

@Jaifroid
Copy link
Member Author

By the way, I'm happy to do the updating myself, but I don't want to edit the document without agreement.

@rgaudin
Copy link
Member

rgaudin commented Nov 14, 2024

Thank you @Jaifroid ; I updated the document.

As the document reflected the decisions made by the Kiwix Board on 2022, I didn't want to add PWA and Electron as-is as it would imply they decided those names. I've added a new section instead.

I believe the discussion in kiwix/kiwix-desktop#1243 might lead to a change as those are Platforms but @kelson42's response was not very clear and we need a clear output from both @kelson42 and @Popolechien to initiate any name change I believe.

@Jaifroid
Copy link
Member Author

Ah, OK, I understand now. I suppose, then, we need to factor in the name "Kiwix JS", which is used for the Browser Extension (at least in the Chrome and Edge add-on stores, whereas the Firefox entry predates the choice of Kiwix JS as the generic name for these apps), and also for the Windows "fork" of Kiwix JS.

I think it might be a bit misleading to tie the app's name to proprietary browsers ("Kiwix Firefox", "Kiwix Edge", "Kiwix Chrome"), as these are all identical apps and code (and there are many other browsers they work on: IceCat, Vivaldi, Brave, Opera...). There might be a case for simplifying it all just to three names. I'd propose:

  • "Kiwix JS" (for all browser extensions and all Store entries, including the Microsoft Store)
  • "Kiwix PWA" (for the PWA not installed form any Store)
  • "Kiwix Electron" (when installed with standalone self-updating Electron installer, or portable AppImage etc., from GitHub)

For those who like history: the original JS app and Repo were known as "Kiwix HTML5". Before I started publishing the then UWP "fork" of the app in the MS Store, mossroy, @kelson42 and I agreed a change of name to "Kiwix JS", since "HTML5" could date too quickly and was too technical for most people. So, that's why it appears as "Kiwix JS" only in the MS Store, and the Chrome and Edge stores.

@rgaudin
Copy link
Member

rgaudin commented Nov 14, 2024

👀
Image

Ah @Jaifroid, your solutions are always at the fringe of the others 😀
We can't directly apply the Kiwix for {Platform} pattern here as PWA is not a platform but a technical media ; same for Electron. (Kiwix via PWA?).

Maybe we should add that to the branding/icon meeting I mentioned in another ticket. We can thus decide collectively if/what/how/when to do with it. Software identity is important and subtle. There's not rush though.

@Jaifroid
Copy link
Member Author

Ah @Jaifroid, your solutions are always at the fringe of the others 😀
We can't directly apply the Kiwix for {Platform} pattern here as PWA is not a platform but a technical media ; same for Electron. (Kiwix via PWA?).

Just so you know, @kelson42 put those buttons there, not me! Again, a few years ago...

@Jaifroid
Copy link
Member Author

We can't directly apply the Kiwix for {Platform} pattern here as PWA is not a platform but a technical media ; same for Electron. (Kiwix via PWA?).

I've got no problem with "Kiwix PWA" and "Kiwix Electron" (without "for"), and/or "Kiwix Browser Extension".

It's a bit trickier with "Kiwix Firefox". That might imply a Kiwix-branded version of Firefox... ISTM that could get us into trouble, at least with brands such as "Kiwix Chrome" and "Kiwix Edge". In this sense, "Kiwix for Firefox", "Kiwix for Chrome", etc. seem arguably less risky to me, especially if we're only using that as a link to the Kiwix entry in the Firefox Add-On Store, etc. What's your advice, @Popolechien?

@Popolechien
Copy link
Member

Kiwix for Firefox (or Chrome, or Edge) seems indeed the logical choice in that regard.

@rgaudin
Copy link
Member

rgaudin commented Nov 18, 2024

Let's pause this discussion and have a call instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants