Shows as installable on mobile, but doesn't work well

[cassidyjames]

Out of morbid curiosity I decided to try Key on my GNOME phone. It installed and sort of worked, but the UI is pretty unusable on the form factor.

We should be able to use AppStream metainfo to note the recommended minimum window size, so app store clients can filter it out appropriately.

[dbnicholson]

That's interesting because I test the Android build in a Pixel emulator all the time. There are a few warts but it mostly looks good. Obviously, WebKit and Android Webview (Chrome) are different web engines, though. Or maybe it's more GTK vs the Android graphics toolkit (Skia?).

[cassidyjames]

I'll have to grab my screenshots off my GNOME phone, but it's pretty much not usable; things are SO cramped that it's not a good experience. But yeah, it's possible something is being rendered incorrectly between engines.

[dylanmccall]

Ehhh, we might just be looking for different things. Looks good and works good aren't necessarily friends :b The narrow window experience for me is definitely pretty bad. It gets problematic that the Discovery page wants you to casually scroll content in two different directions: arrows to scroll all these carousels left and right, and then a bunch of vertical scrolling to get to all the different carousels. Even if we're really attached to the carousels, I think once we get down to two columns they should change to plain old unconstrained lists of content that overlow vertically. Definitely at one column. Until we're really looking at mobile as a use case, I agree it makes sense to set our metadata accordingly.

These arrows take up a lot of space, and they make me pretty uneasy: