Pause creating apps in flatpaks until CLI interoperability improves

I'm looking to package about 10-15 flatpak CLI apps. Mostly GoLang/Kubernetes specific CLIs. On Linux most maintainers of their software are just giving you a static binary and \`brew\` option. I'm not a fan of either. So I figured I'll take it upon myself to get these in a flatpak and slowly raise issues with all the maintainers to flatpak them and help them if necessary get it to flathub. I just did my first demo with [Flux](https://github.com/fluxcd/flux2). My first thought was, online builds are easy pz, I'll be done with this in no-time! Then realized ... that even if I export `~/.local/share/flatpak/exports/bin` to my path I still need to call these commands with the FQDN or rather .. FQCN ? Either way not `flux` but `io.flucd.flux` In a lot of these applications there already open requests to have there app in a flatpak. I just can't see users wanting to already type a long command or manually add aliases for every single tool they want/need to use.

​

Before I take my efforts to OBS and spend considerably more time on this does anyone have any good workarounds or ideas to solve this problem? Again, I'd like to manage these myself so I can use them immediately and for anyone else willing (with the idea of deploying flat-manager) until they're properly accepted into flathub.