Your comments

What potentially is a bug with GCDroid from all the above is that I think you can't use the menu option to "open in web browser" if that link has been associated to always open in GCDroid. But I am not 100% certain and I can't test it now when I am at Android 12.

Sounds good to me. I would suggest default zoom value to be the same as when the geocache icons are switched. If you want X to be user-defined that is. Otherwise just hard-code it to the zoom value changing the geocache icons.

Potentially a user might want this as an option per map type, since the colors of the map types makes it more or less interesting to use. But personally I think that's overdoing it, I would probably prefer a global option myself.

Probably not if it's complex. :)

But it is annoying to have several months old data. This wasn't an issue when I geocached more, then they used to disappear by themselves (due to more usage, over a larger area, due to more traveling). I guess I just have to be more cautious in the future.

My suggestion was to show it on the view that has cache information though. The one with logs tab, friends tab and so on. I assume you only have one date stored here, from when you fetched geocache information. The logs itself are attached from that of course.

Maybe it would look decent to add it over/by the refresh icon?

Probably my mistake, seems like I already had that geocache loaded/cached from before I made that note. Didn't find a way to close/delete this myself.

Without a doubt "31 august 2001". How that is chosen I do not know, but for me locale and date format is about the format, not translations.

How realistic it is to implement this in a generic, clean and decent way, I do not know. With your points above I really see how it's not that simple. On the other hand I am surprised that it's not simple. This should in my opinion be an issue for about a huge crowd in the Android world. But more on an OS level than app level.

Now when I think about it, I do use a few apps where I choose Date format actually. Tried to click though a few, the first one I thought about had a setting for it, the next two didn't. I probably have it in more, but hard to imaging which. The one that had only used one length. It's UI design might have more room though, because I can choose both long and short formats there. MM/DD/YYYY in its 3 combinations. All three with dots instead of slash. And then three text strings similar to "Tue, Dec 31, 2019". But to be clear, that app has ONE setting. So I either use numeric only, or longer strings only.

All in all I see your points and I realize that this might not be as simple as I had thought.

According to this ticket c:geo doesn't seem to support custom date formats either; https://github.com/cgeo/cgeo/issues/6609

I see your points, they are definitely valid. Would be easier if it was an OS setting. Also I don't know Java, so thank your for pointing out its three different formats/lengths.

If you are only using short format you could just let the user chose between YMD MDY DMY, but if you later on implement a longer format somewhere, then that's a mess.

I guess I am out of creative and realistic ideas. Maybe someone else will have some insight. If not, I might be the only one in the world who cares. :)

It doesn't make sense to me. Android only supports changing language, might be though as locale though. But Android never shows any dates in either YMD, MDY, DMY from what I can find, therefore such setting isn't needed. I would of course prefer if Android supported changing locales, just as one can do in any computer operating system.

I can understand if you don't think its worth your time though. But the fact that I need to run my whole phone and therefore also many apps in for example Swedish to get a readable date format is just weird. It's the honest truth that every time I look at a date in the logbook I have to scroll to a log that shows a day >= 12 to know the format. I have also interpreted log dates wrong more than once.

I just checked what date format I have in the phone. Since I run it in US English, for various reasons, I "obviously" use MDY, which seems to be used by about 5% of the earths population. :) As a former German I would expect you to feel the same issue. But maybe you are used to running your OS in German?

Still, it's not the most important thing in the world, but it is something that has annoyed me over a hundred times over the years with GCDroid actually. Most of all I am curious how the other geocaching apps handles it, not the least the official one actually.

PS! The setting in Android is called language and not locale. If that controls locales as well, they (not you) should fix that. But I don't think either of us will be able to affect Google on that matter.