Matthias Klumpp

> Wouldn't requirements be better anyway? That's probably what I would go with... It's called "requires" because that's what the tag name is in metadata and it jives well with...

> > * App does not need an internet connection. (Example: Encyclopedia on Endless OS, [Contrast](https://flathub.org/apps/details/org.gnome.design.Contrast), [Teleport](https://flathub.org/apps/details/com.frac_tion.teleport)) > > This can’t be represented in my proposal above. Perhaps we need...

I think it's actually okay for GNOME Software to simply say it doesn't know about certain data, rather than guessing. Instead of adding any "not" directives, we could also version...

> This still feels a bit odd to me. In particular , which reads to me as “this requires the internet, lol no it actually doesn’t use it at all”....

That has *always* been more reasonable ;-) A proper generally applicable solution is so much better than using a custom, project-specific hack. I still think @pwithnall 's last suggestion is...

Hey :-) So, first of all: I acknowledge the problem - this is something I have thought about already, but I haven't found a solution for this yet. Implementing something...

What kind of features to do you have in mind? I can't think of any feature value that would apply to every single application, besides stuff like crash-reporting, which the...

The prior art is indeed interesting! Having this as a separate block would be an extremely disruptive change... Maybe in future if we allowed developers to tag paragraphs and lists...

We can't remove the named values, but we can always change what they mean, as that is exactly their intended purpose (for apps which are fully adaptive and really don't...

This markup mimics prior art from Android, which also allows both: https://developer.android.com/guide/topics/manifest/supports-screens-element (Android also scales apps up if they don't fit into large screens, which is of course not desirable...