It's using the MLMYM frontend, which you can actually use via the official MLMYM website with any instance. For example, here is it pointing to lemmy.ml:
I generally prefer the UI of Apple Maps (Google is way too cluttered), but Google has much more complete review data, hours, and menus, so I usually end up using Google.
Anyway, I wasn’t aware that GIMP UX suffers, I’ve never used anything else and am happy with it.
My argument here is that by never having used anything else, you wouldn't necessarily realize how much better other UX choices could have been.
That said, I do have to give the devs some credit, as they have fixed two major issues, by adding single-window-mode and unifying the transform tools. Having each transform be its own separate tool was just awful UX IMO.
The biggest remaining UX problem, in my opinion, is the way GIMP forces layers to have fixed boundaries. Literally no other layer-based image editor has fixed layer boundaries, because it makes very little sense as a concept. Layers should solely be defined by their content, not by arbitrary layer properties set in a dialog box.
Honestly I feel like this attitude is the reason GIMP’s UX suffers. They’re so determined to be “not like photoshop” that they’re unwilling to fix some of their more boneheaded UI decisions out of fear that they’d be seen as copying photoshop.
I think so, I believe you can open them in Books via the Files app on iOS.