One of the greatest aspects of the Snap daemon is that I can choose to have all of my software install from the most recent “track”/channel (of which four are default: “stable”, “beta”, “candidate”, and “edge”, which have been ordered as descending stability but ascending newness from right-to-left) using a flag such as --channel=latest/edge during invocation of installation. I am greatly desiring that this functionality be replicated by configuring an order of stability and newness for repositories, so that I shall be able to, in a script, state that one application that is packaged as Flatpak shall be downloaded primarily from http://nightly.gnome.org/gnome-nightly.flatpakrepo or http://distribute.kde.org/kdeapps.flatpakrepo, but if not available, shall install from http://flathub.org/beta-repo/flathub-beta.flatpakrepo or, if also not available there, http://flathub.org/repo/flathub-beta.flatpakrepo.
This obviously may require co-operation from the developmental team of Flatpak, but I am quite certain that this can be addressed, shall allow much better automation for developers, and shall rid me of the last reason for me to bother to use Snap again.
If I am informed that this is not already possible, I shall create an issue at https://github.com/flatpak/flatpak/issues/new for it, unless I am convinced that this should not be added.
This should somewhat remediate Flathub beta is storing old versions of software.