10
  • Orion Apps (aka Profiles) should be human-readable first and ID/UUID second

  • BugsDesktopPlanned

When working with Orion Apps that are being called "Profiles" one will notice that they are saved in a format similar to the following:

$HOME/Applications/Orion/Orion\ Profiles/B6958EF9-5006-46C1-B190-389B4D696ABD/Orion\ -\ NAME_OF_PROFILE.app

If you parse this out visually / mentally you note that the first levels make sense in terms of human cognition:

  • /Applications/
    • Orion/
      • Orion Profiles/
        • B6958EF9-5006-46C1-B190-389B4D696ABD/ (non-human readable UUID)
          • Orion - NAME_OF_PROFILE.app (aka, human readable / parsable name for app / profile)

But then things slide sideways with having what appears to be a UUID present for a profile identifier instead of a human readable app / profile name. I have, far too many times over the years, found that it is better to put human identifiable attributes first for easy navigation and identification. This is sorely needed when problems arise and one becomes rapidly frustrated if there are many such things to navigate vs having the correct path readily available in a mentally easily parsable fashion since 99/100 when one is looking for such a path, something has already gone wrong. This simply introduces more mental load and frustration that could be resolved early in the game of this feature/functionality.

I think any methodical consideration would yield a similar thought process and thus I consider this likely a simple overside / bug in the implementation vs a feature request.

The expectation would be to have the order reversed for the UUID vs app/profile name, eg, it should be ordered thus (if the UUID is even necessary as a profile identifier, which I suspect it is):

$HOME/Applications/Orion/Orion\ Profiles/Orion\ -\ NAME_OF_PROFILE.app/B6958EF9-5006-46C1-B190-389B4D696ABD/

0.99.126.4.1-beta

Sonoma (14)

    ylluminate This is because profiles can have the same name, which would create a conflict. The UUID is first to prevent naming collisions.

    Why would someone ever want two profiles with the same name? Even if someone did, why not just append a (1) to the second profile app? Profiles already have unique bundle identifiers internally so the functionality wont change

    a month later

    I definitely would opt towards simpler nomenclature such as differentiating via a simple postfix vs utilizing the UUID first. Profiles should not be thought of as "profiles" but as apps. Thinking of them as "profiles" is really a "wrong-think" kind of scenario since these could and should be thought of as application instances that accomplish specific purposes. Having the same profile name, frankly, could be forbidden and that would be also a valid way of handling this.

    3 months later

    When Orion profiles are created in OSX, they should be registered with more user-friendly names.

    When using defaultbrowser, I get this:

    10:37:41 › defaultbrowser
      iterm2
      1f701df5-eb5b-44b0-992e-6c2b277be9ab
      safari
      e265c201-c95d-4920-a413-7d894d23a118
      browser
      kagimacos
      2fc07e81-a6d4-4b09-92f1-c63edb497811

    When using defbro, I get this:

    11:05:20 › defbro
      com.kagi.kagimacOS.E265C201-C95D-4920-A413-7D894D23A118 (unknown)
      com.kagi.kagimacOS.2FC07E81-A6D4-4B09-92F1-C63EDB497811 (unknown)
      com.kagi.kagimacOS.1F701DF5-EB5B-44B0-992E-6C2B277BE9AB (unknown)
      com.kagi.kagimacOS (Orion)
      com.googlecode.iterm2 (iTerm2)
    * com.brave.Browser (Brave Browser)
      com.apple.Safari (Safari)

    I believe that the UUIDs are Orion Profiles, while kagimacos is the base Orion Browser? (From other sites, it appears that Brave registers itself as browser. <smh>)

    Given the current profile naming, I would need to use trial and error to find the right one. Ideally, the system profile names would be more human-friendly.

      For example Firefox does this my profile I call reading is avdjnlh0.Reading on the disk.

      So orion profiles could the UUID.<user given name>

        The profiles are internally identified by these UUIDs. This allows for profiles with the same name, as well as being able to easily rename profiles.

        If the profiles were identified as UUID.{name}, then it could get confusing when renaming profiles. How does firefox handle profile renames?

          IMO defaultbrowser's implementation isn't the best because it only looks at the last element of the bundle id (the unique id for each app, also what defbro prints out).

          What brave does is actually pretty reasonable, as the full bundle identifier is named normally, just that the last part of it is just a generic name.

            By going to ~/Applications/Orion Profiles, each profile is then located under another folder, which is the profile's bundle id.

              I remember there was another thread discussing profilie naming, can someone find it so we can merge?

                @laiz @Vlad I think that post is unrelated bc that issue concerns the path the profile is located, while this issue focuses on the readability of the bundle id

                  Merged 8 posts from Better naming for Profiles.
                    4 months later

                    Any news on how soon we might see this? Thinking about using Orion more heavily, but don't want to make the switch until I can have clean browsers under a clean folder structure to be able to easily click on a folder and see all of my dedicated isolated browsers like I can with Coherence X. Makes it much easier to have dozens of isolated browsers as is actually best practice on the web today.

                    Also, fwiw, Choosy (https://choosy.app/) is amazing in managing browser defaults in macOS. Far better than any other options I've found and facilitates a very clean and orderly web/internet experience holistically. Choosy coupled with Orion Apps will be AMAZING!!!.

                    4 months later

                    Hi @Vlad has there been any progress on this front? I and a few other folks have grown weary of other browser options as of late and are starting to warm up to shifting entirely over to Orion... I'm really hoping to see this in place sooner than later.

                    BTW, you can move the profile apps to a different location, and they will still work fine

                      No one is typing