I also use it like this. I got into it for the sandboxing, although I know there are a "few" lurking issues on this point. But, some of the sandboxing definitel

I also use it like this. I got into it for the sandboxing, although I know there are a "few" lurking issues on this point. But, some of the sandboxing definitely works, and were I a flatpak engineer I'd want to see some indication of traction to justify working towards goals of completion, and no other project with any packaging base I can think of is anywhere close, so, I use it. In fact...I think I have all the software packages you have, except Obsidian, but also, Signal, Anki, and Element. I did consider using it to deploy and update a CLI on (multiple) Linux(es), but found that the design of common shells make that kind of thing uncomfortable, as you need to teach them about autocompletion and the user also has to muck with getting the utility into $PATH. Normal-style packages simply have the privileges to muck with /etc and /usr/bin and that's the end of that, but it is somewhat unsatisfying that this is almost necessarily the case.