Make extension manager more transparent and clear: Show extension origin + update source

LexFradski

Problem

In Tools > Extensions > Manage Extensions... Orion shows a list of installed extensions and their type (Safari / Firefox / Chrome), but there’s no easy way to see where an extension came from:

For Web Store installs: Web Store ID, and a link to the original store listing
For local installs (e.g. .crx, .app): the original file/folder path, or at least what Orion considers the current source location

This makes troubleshooting and reporting issues harder (e.g. reporting compatibility bugs right here, on this board), and also makes it difficult to share simple link to extension with other users.

Update behavior is unclear

Also from the current Extensions UI it’s not clear how Orion automatic updates mechanism works. Some examples/questions:

If I install a Chrome extension from a .crx file and it’s shown as a Chrome extension:
- Will Orion update it from the Chrome Web Store if the extension ID matches?
- Or will it only update from the local file path (and what happens if that file is moved)?
What is the update mechanism for Safari extensions?
- If I disable automatic updates for a Safari extension, what does that actually do in Orion?
- If the extension is distributed via Mac App Store: does Orion simply pick up the new version after the app updates, or do I need to press an Update button inside Orion?
- What about Safari extensions installed not from Mac App Store (e.g. via Homebrew or Sparkle)? Where does Orion check, and how does it detect updates?

My suggestion

Show share link origin/source in extension settings menu: Options, Console, Permissions;
Do not update; Open in Web Store, Share.
Show update channel + current update source (store vs local file vs app bundle vs wtf)
Provide a clear, user-facing explanation of the update rules for each extension type

LexFradski

Concept-art

Yannick

That's a good idea. Thanks for taking the time to make some mockups 🥳