(thinking) is solution for usual user immutable woes better flatpak?

I’ve done immutable distro hopping, all the ways to make apps run, and even tried custom ublue image.

Few cases seem too messy as of right now to be accesible for non-techy users: 1password limited on flatpak vs layering or ujust script. steam and gamescope, unless baked with os, also hit some limitations.

I’ve been thinking about this and i feel like i’m missing some linux history here - flatpak should have solved this with sandboxing and permissions, right? like, 1password should ask for fingerprint scanner permission, communicate with other apps (browser) permission.

Is flatpak improvement where ease of use will be for immutable distros? Or is there something I’m missing that’s blocking this?

(if i sound naive, it’s probably lack of history/context - I’m more aware of how things work, but less of why)

1 Like

accesible for non-techy users

Are we expecting non-techy users to install Linux? :grinning_face_with_smiling_eyes:

None of this stuff has anything to do with the immutability of the filesystem (or distributions!), it’s a matter of getting browsers and password managers more involved in modern linux app development by working via a flatpak portal so that it all works out of the box.

1 Like

/facepalm you’re right, i was so used to going with default install methods (usually .rpm), but there’s no reason why app devs couldn’t invest more in flatpak and feature it more. usually flatpak is on the bottom with “well, if you must, but it won’t all work well, lol, xoxoxo”

i’ll do my part in posting on their respective forums about supporting flatpaks to show interest