You'll note that I asked about "how **the
image linked above** could
be considered helpful to a reader." (emphasis added; that image was
https://commons.wikimedia.org/wiki/File:Wikipedia_mobile_app_beta_bug_-_201…
) - indeed, you refer to my 'specific' query.
Are you really saying that you tested that image? (Or even anything like it?)
Or did you test using images where the cropping applied didn't result
in such inanity?
From a developers point of view catching every possible
edge case is
difficult to do first time round but I have every confidence in the
app development team that these examples are in a minority and this
will improve over time.
I'm not sure where the image comes from right now but in future I
envision this is also part of the editorial process and editors can
help with this by choosing appropriate images, optimising for this
sort of display (maybe a Wikidata app image property).
Thinking out loud here but really what I'm saying is I'm happy to see
us innovating, and I don't think we should get too distressed by
certain cases which don't quite work, software is never done. We hit
similar issues early on with the nearby feature for mobil web where we
had instances of articles that were not nearby showing up in the UI
and being incorrectly positioned due to problems with the API. As a
result apps were able to get the nearby feature in really easily and
even added a cool orientation aspect to push it to the next level!
With people raising these bugs the software got better and the end
result even more so.