I completely forgot about this mode in #Adwaita apps. You can press Ctrl+Shift+M and test how your app works on phone screens from the comfort of your desktop. This is gold!
I completely forgot about this mode in #Adwaita apps. You can press Ctrl+Shift+M and test how your app works on phone screens from the comfort of your desktop. This is gold!
I had jrb, maintainer of the GNOME app 'Crosswords' over for espresso and dinner and he showed me something really cool - Crosswords running on an android as a native app with no design changes - libadwaita just worked in the phone profile.
That's some epic engineering y'all, kudos to @alice and others involved in making this happen.
Disclaimer: my post was just about libadwaita working as it should not about it working in android. Alice knows nothing about Android.
Hm it feels like that at some point in the last (half) year people started to build very complex interfaces with libadwaita. Is there a reason for this?
@argv_minus_one Yes.
When I introduced the adaptive apps UI design term in GNOME (through a blog post launching the development of the companion GUI toolkit widget libraries we have today) ~10 years ago, that was the goal.
Now there's even a formfactor simulator in the Inspector: https://blogs.gnome.org/alicem/2024/12/19/mobile-testing-in-libadwaita/
Many GNOME apps using #libadwaita are designed to "adapt" to the device formfactor that way; GNOME Calendar, Showtime, Secrets, Warehouse, are good examples of adaptive GUIs besides Web.

Lately I’ve been working on touch controls overlays in Highscore1, and quickly found out that previewing them across different screen sizes is rather tedious. Currently we have two ways of testing UIs on a different screen size – resize the window, or run the app on that device. Generally when developing, I do the former...
NOT A FUCKING HOT TAKE.
#Gnome #GTK and #libadwaita have ALWAYS been historically pretty disrespectful and dismissive of anyone who uses their libraries and does not comply with their latest dictates.
It'd be great if #GTK & #libadwaita's About dialogs had a property for "Months of support per version", which would check the app's running version against its "date" field in the AppData metainfo.xml and hide the "Website" & "Report an Issue" buttons if it's too old.
Thus upstream devs could avoid being the externalized cost of free "LTS" distros (users reporting issues about ancient versions) without being accused of being anti #FLOSS (like in https://gitlab.com/linuxmint/pins/mint/gnome-calendar/-/work_items/1)