Developers of apps on Flathub, some questions for you!
First, what's your app? Why did you choose Flathub to distribute your app? Do you distribute on other stores/distribution methods, or just Flathub—and why? What's something you like about Flathub? What's something that could be better?
Anyone fancy some API and data wrangling? I’m trying to compile some interesting statistics for Flathub, and something I would like to know: how has the rate of verifying new apps changed over time (or is there even enough data to calculate that)?
For example, when we first introduced verification, were most new apps being verified? With new apps submitted now, are they more likely to be verified?
It just seems like an interesting thing to know. :)
While this also adds a bunch of new features like language and subtitle selection it mostly moved things closer to the designs. We have a wide mode for docked/desktop mode now and autohiding of panels, etc.
Flathub is the place to get apps for Linux, and it’s getting even better!
Endless OS exclusively uses Flatpak for apps with Flathub as the default source in App Center, so we’re thrilled to see the bar continuously raised for the quantity, quality, and ease of discovery of apps.
Read about the latest initiatives to continue to raise the bar: new app metadata guidelines and the path towards curation.
Working on a little thing for Home Assistant that I hope to submit to Flathub soon. Not really all that special or complex, but I don't love how PWAs are handled by any browser on Linux, and I want to eventually add some more interesting functionality to the header to make it feel even more native... but this is a start.
@cassidy
I agree the system as it is now is not user-friendly. But at least the system works as expected.
Example: Say i have an install script for flatpak apps on fresh machines.
The first day all is fine because the names are unique, then somebody creates a similar app and the script is sent to the search page.
Better implememt a daemon that can open flatpak:// links or something and install apps from the browser, than copy & paste to console.
Users of Evolution from #Flathub may have noticed that it is still stuck on 3.50.1. This is because the 3.50.2 build got stuck on lint checks.
We have removed permissions that seemed unnecessary, but you never know. If you're using Evolution from the beta channel, let us know if you have any problems with GPG and PKI support. We'd like to know any user impact before pushing it to stable.
I wish #flathub would use the appstream:// protocol by default in a "Show in store" button, with an option to switch to the flatpakref.
It feels like a horrible UX to click "Install" on the website, to download a file that will (on click) open the store where I again have to click on "Install" for the thing.
Today I'm attempting to exclusively use the Pinebook Pro (running Endless OS!) for work, and it has actually gone better than expected. At the same time, dang, we're still lacking in a few ways on ARM; notably, app availability! How is Firefox not available on Flathub for ARM64??
After a long work, the new version of Midori using GeckoView will be ready before the end of the year before the holidays, arriving just in time to protect thousands of users.