Hello! To start, I want to say that Solus 4.4 is very good. I'm really liking it.
I'd like to make a couple of suggestions for the next major release (hopefully).

Please add a couple of toggles to the Software Center (in the Settings section):
1) Enable/Disable Flatpaks
2) Enable/Disable Snaps

Once enabled, the Software Center would then add two more categories (in the pane on the left):
1) Snap Packages (if enabled)
2) Flatpaks (if enabled)

This way, those packages are more-easily filtered for end users to search through.

Finally, when Snaps and/or Flatpaks are enabled, the Solus Software Center could then be used to install those packages. Having a graphical process (via the Solus Software Center) would add just the right amount of spit and polish to attract even more users to Solus.

My current process is to navigate to Snapcraft and Flathub via the browser and then run the install from the Terminal. Again, it's not a showstopper for me, but I would choose the Solus Software Center over using the Terminal if I had the option as it would also make uninstalling packages that much easier.

Thanks!

There was a planned rewrite of the software center to include flatpak, and maybe snap packages, at some point.

Personally, I prefer browsing for apps and viewing info about them through the terminal. To each their own.

    Brucehankins wouldn't changelog be a treat in eopkg info package1?🙂. What kind of other commands do you use besides info to avoid the Software Center gui? (thanks Bruce!)

        brent mostly the basic ones, search (sr) , remove-orphans (rmo), list-upgrades (lu), sometimes list-components (lc). My needs for packages are pretty low, and if I'm really trying to decide between something like digikam or shotwell, I'm going to look at what dependencies are being brought in and which integrates with my DE best. I'll also probably look at reviews and such on the web before that point anyway.

        It would be nice to see the changelog though, for apps outside of the mozilla-sphere, there isn't such wide coverage of changes, so it can be hard to find sometimes. Though, to be fair, I only list one or two things and then a link out, so.....

          elfprince

          If I were to guess it would be from its intended usage and is likely a term borrowed from source code management systems which have long used blame for finding who made a specific change and when; Example: git blame filename not really seen as a negative in this context.