-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve support for phone apps #4020
Comments
Open an issue in https://github.com/flathub-infra/documentation
Appstream does not have the metadata fields to tell which screenshots are meant for which devices, so the website cannot filter like that. Only the search filters seems to be a new feature request here. |
|
Thank you for the information, I already know that there is currently no possibility in the Appstream spec to set the form factor for a screenshot. It is more a general idea without the exact implementation / feasibility already known. Maybe it could be discussed upstream at the Appstream repo whether and how the screenshots could be distinguished. Currently, a way to guess the form factor of the screenshot is by using its resolution: If the width is bigger than the height it is landscape and therefore probably a desktop screenshot. If the height is bigger than the width it is portrait and maybe a phone screenshot. |
No guessing like that is unreliable, there are apps/games which have height > width on desktop. You should discuss it in the appstream repo. |
Although Flathub contains more than 250 apps suited for (GNU/)Linux phones (filter for "'mobile fit' 'equals' '5'" and "'distributions' 'contains' 'flathub'" at https://linuxphoneapps.org/find/apps/ to see the number of apps at the bottom of the page), it currently lacks some important functions to better support phone apps.
Therefore I propose to implement these improvements:
This issue is for discussing the general idea of improving support for phone apps. If necessary, I could split up the proposed improvements into single issues to discuss them in more detail.
I think about applying for NLnet (https://nlnet.nl) funding in the December round in order to implement these improvements.
The text was updated successfully, but these errors were encountered: