IIRC that's the whole point of flatpak, snap and appimage
Docker can probably do it too, distrobox puts a useful wrapper on that
Nix does that kind of, nix packages aren't isolated in that they can't access resources on your system but all dependencies are stored in the nix store, hashed and isolated from eachother, and wiped when you collect garbage
Go with one of the ready to use systems. Flatpak, Snap, AppImage. Snap is largely Ubuntu Ecosystem, Flatpak is independent. AppImage is an option if you do not need/want a Sandbox.
Stay away from Docker and LXC for this use case (graphical applications), they are much more work to get going.
One way or another, if you want to run an application you are gonna need its dependencies (the key is the name)... they may be bundled into an appimage or come as part of flatpak ruintime, or be confined inside a container, or live in the nix store, but they will "bloat" your system anyway.
Learn how to cleanup your system (ie. uninstall all packages that are not needed by others that have been requested explicitly) and live a happy life. Only bother with other solutions if the software (or version) you need isn't available for your distro.
You can use appimages, more importantly if you make a directory next to the appimage with the name of the appimage + .home the appimage will also set that as its $HOME that way you can also keep the configuration files of the app separated from the host OS.
Both strange and not, tbh. On one hand, I understand the sentiment; on the other hand, installing more software with its own dependencies to isolate electron's dependencies, and potentially installing twice those libs both electron and something else on your system depend on seems counterproductive (leaving the security benefits of containerization/sandboxing out of the question here, tho).
Points for the correct answer. I work on systems for spacecraft and podman is what we use on those for containerization (better option for a couple reasons)... but we literally just SAY docker to the suits, because that's what they've heard of. Which is why I said docker to this guy.
Docker and podman aren't too bad nowadays I don't think assuming you're not running something huge
They are basically like throwaway mini-vms that contain one application to ensure it will always run no matter where so long as the machine you're running them on can run docker
They can run CLI stuff just fine, I'm not sure about desktop apps someone smarter than me will probably tell you about that
Docker and Podman are both free. Podman is the lighter weight, more FOSS, also slightly more DIY option, they are intercompatible - I work on systems for spacecraft and Podman is what we use on those because it's lighter weight. If you want to run something in docker, ChatGPT is actually pretty good at talking you through the specific setup (at least that's been my experience).
It depends on your usecase. We need more detail regarding what application (gui/cui/open source/proprietary/custom) you are trying to use
Check if the application you want to use exists as snap/flatpak/appimage.
If it exists, install the application as per their standard operating mechansim
Once used, just remove them. Your original system libs are untouched
If the application doesn't exist in those platforms, it's a different story. You might need to use distrobox or docker. Don't use nix because it's overkill for what you want to do.