Geocaching apps for Android: what to check before you rely on one

Choose a geocaching app for the place, not the feature list

Comparisons of geocaching apps usually turn into feature tables, and feature tables are the wrong tool. Almost every app can show a map, show a listing and log a find. The same is true on iPhone, where the shelf is shorter. The differences that decide whether a day goes well are narrower and duller than the marketing suggests.

The first is whether the app works with no connection. The second is how it behaves when the battery gets low. The third is whether it supports the listing service you actually use. Everything else — themes, statistics, badge systems, is preference.

Offline is the dividing line on Android

An app that needs a connection is a different tool from one that does not, and the difference only appears when it is too late to fix.

Offline means two separate things and both must be true. Offline maps means the tiles for your area are stored on the device. Offline listings means the cache descriptions, hints and previous logs are stored too. An app can do the first and not the second, which leaves you with a beautiful map and a row of caches you cannot read anything about.

Test both before you rely on them. Download your area at home, put the phone into airplane mode, and walk through the actual workflow: open the map, pan to where you are going, open a listing, read the hint, open the recent logs. If any step needs a connection, you have found it in your kitchen rather than on a hillside.

Battery is the constraint nobody plans for

Continuous positioning with the screen lit is close to the heaviest sustained load a phone carries. A full day of caching will flatten most phones, and it will do it faster in the cold.

Two habits help more than any setting. The first is screen discipline: get a bearing, put the phone away, walk, take it out again near the site. Watching the arrow for a kilometre costs a large share of your remaining day. The second is carrying a power bank and treating it as core equipment rather than a precaution. The same way you would treat a pen.

If the phone is also your map home, your torch and your way of calling somebody, its battery is a safety item and not just a convenience. That is covered in more depth in the safety section.

Which service the app speaks

This is where the alternative listing services become a practical rather than philosophical concern.

Some Android apps support several services. Many support exactly one. If you use a national Opencaching node alongside the larger service, check that your app can see both before building a route that mixes them: otherwise you end up with two apps, two maps and a day spent switching.

It is a small friction and it is one of the quieter reasons single-service caching persists even in countries where the alternatives are healthy.

What a good setup looks like

For most people, on Android, the arrangement that survives contact with reality is unglamorous: the official app for whichever service they use, offline maps downloaded for the region they cache in, a power bank in the bag, and one paper backup of the day’s coordinates in case the phone dies entirely.

That last item sounds excessive until the first time it happens.

One setting worth checking

Before a day out, confirm the app is not set to hide caches you have already found. It is a sensible default that occasionally hides the wrong thing: a cache you logged a DNF on, or one you found years ago and would happily revisit.

Permissions, and the setting that quietly breaks everything

Android’s location permissions have tightened repeatedly, and the change that catches cachers is the distinction between location while using the app and location all the time.

For finding a cache, while-using is enough and is the right choice. The setting that matters more is battery optimisation: an app aggressively suspended in the background will stop logging a track, stop delivering notifications for new caches, and occasionally hand back a stale position when you bring it forward. The symptom looks like poor accuracy and is not.

If an app behaves well in the hand and badly the moment the screen locks, that is the place to look before blaming the receiver.

When the map and the listing disagree

A cache that plots in a river, on the wrong side of a fence, or fifty metres into a field is usually not a mis-set coordinate. It is a basemap that disagrees with reality.

Different apps draw from different map sources, and those sources are updated on their own schedules by their own contributors. A path re-routed two years ago may exist on one and not the other. The coordinates themselves are a pair of numbers and do not move; what moves is the picture drawn underneath them.

When the two conflict, trust the numbers and the ground, not the rendering. And if a map error is consistent and obvious, the underlying map is usually community-edited and will accept a correction — which fixes it for everybody who walks there afterwards.