wanderer

Every GPS track a hiker records is a small piece of personal history: the ridge walked in fog, the bailout route, the summit finally reached. Many trail platforms keep that history on their own servers and on their own terms. wanderer, from developer openwanderer, reverses that arrangement. It is a free, open-source, self-hosted trail catalogue with no paywall and no subscription. It is built to organize, plan and share GPS tracks from a server the user controls, or from an existing community instance for anyone who would rather not run one.

The web platform does most of the work. It imports GPX, KML, FIT and TCX files and draws new routes through Valhalla-powered planning. Each trail can hold metadata, photos, waypoints, elevation profiles, statistics and tags. Search works both as full-text queries and across the map, with filters, custom lists and summit logs on top. The social layer runs on ActivityPub federation, so following, liking, commenting and publishing work across independent instances instead of inside one company’s walled garden.

The Android app covered here is the companion piece. It is a public beta that adds GPS recording, turn-by-turn navigation and offline maps, and it requires an account on an instance running a compatible server version. It ships through Google Play’s open testing track, and the community around it is still small. Early commentary on Product Hunt and Lemmy praises the independence, privacy, clean design and elevation-aware route planning. It also flags the work of maintaining a self-hosted server, and some commenters see wanderer as a better archive and planner than trail navigator. That split frames this review: the foundation is solid, and the mobile client is still catching up to it.

• Multi-Format Import: GPX, KML, FIT and TCX uploads bring tracks from different devices and services into one catalogue.
• Valhalla-Powered Route Planning: New routes can be drawn, not only imported from past recordings.
• Rich Trail Records: Every trail can carry metadata, photos, waypoints, elevation profiles, statistics and tags.
• Search and Organization: Full-text search, map-based search, filters, custom lists and summit logs.
• ActivityPub Federation: Follow explorers and trails on other instances, like and comment on trails, share lists and publish trails publicly.
• Plugins and Open Export: A plugin system handles extras such as Strava imports, and data exports in open formats.
• Android Field Tools (Beta): GPS recording, turn-by-turn navigation, offline trails and map regions, and background recordings that upload automatically once the instance is reachable.

A Catalogue Built to Grow

The design assumes a collection that keeps growing for years, and almost every feature serves that assumption. Four import formats (GPX, KML, FIT and TCX) let exports from different devices and services land in one place without conversion work. Each trail then becomes a full record rather than a bare polyline, with photos, waypoints, an elevation profile, statistics and tags stored next to the route.

Retrieval gets equal attention, which is the correct call:

• Full-text search finds a trail by what was written about it.
• Map-based search finds it by where it is.
• Filters narrow either result.
• Custom lists and summit logs add curated structure on top.

A track archive without solid retrieval turns into a junk drawer once it passes a few hundred entries. wanderer treats search and organization as core features, which is what a long-term home for outdoor history needs.

Planning That Accounts for the Climb

Route creation runs on Valhalla-powered planning, so new trails can be drawn instead of only imported. Commenters on Product Hunt and Lemmy single out the route planner and its elevation view, and the pairing makes sense. In the mountains, distance alone misrepresents effort, and a planner that shows the vertical profile answers the first question hikers ask. Drawn routes and uploaded tracks become the same kind of trail record, so planning and archiving happen in one workflow rather than two separate tools.

Federation Instead of a Platform

The social layer is wanderer’s most distinctive bet. Built on ActivityPub, it lets people follow explorers and individual trails on other instances, like and comment on trails, share lists and publish trails publicly. Following a trail, not only a person, is an unusual choice. It suits a domain where the route often matters more than who posted it.

The trade-off is reach. Federation spreads the community across independently run servers, so discovery depends on how many instances exist and how active their members are. The community is early-stage, so discovery remains limited. Users get a social graph that no single company can revoke, but they do not get a large, ready-made audience. For a privacy-minded hiker sharing with a club or a circle of friends, that trade is the right one. For someone hunting crowd-sourced route reports on popular trails, the network is too thin to replace a large commercial community today.

Self-Hosting: Freedom With an Upkeep Bill

Users choose between running their own server and signing in to an existing instance. Running a server delivers the full promise:

• Tracks, photos and logs stay on hardware the user controls.
• A plugin system handles extras such as Strava imports.
• Open-format export keeps the exit door unlocked.

Lock-in is designed out.

The cost is administration. One Lemmy user reported that Docker updates broke their instance and later the web component. That is a standard risk for any self-hosted service, but a real one for hikers who are not also sysadmins. The mobile app adds its own dependency: it needs a compatible instance version, so users on a community server must wait for that server’s administrator to upgrade. Joining an existing instance removes the maintenance work but moves trust to whoever runs it, which partly brings back the dependence wanderer exists to remove. We consider this an honest trade rather than a flaw, but newcomers should go in clear-eyed.

The Android App: A Field Companion in Beta

The companion app supplies what a web catalogue cannot: GPS recording, turn-by-turn navigation, and offline trails and map regions. Its sync model suits backcountry use. Background recordings upload automatically once the instance is reachable, so a weekend without signal does not mean shuffling files by hand afterwards.

The limits are just as clear:

• Read-only features: Comments, summit logs and lists cannot be edited in the app for now, so the social and curation features that define the platform still require the web interface.
• No voice guidance: Turn-by-turn instructions require looking at the screen.
• No rerouting: The app offers no automatic recalculation when a hiker leaves the planned line.

The developers themselves advise against relying on the app as the only navigation tool, and we agree. Treat it as a recorder and offline reference, and carry an independent backup. Some early commenters already describe wanderer as an archive and planning tool rather than a trail navigator, and the app’s current feature set supports that reading.

Commenters on Product Hunt and Lemmy describe the design as clean, and the feature set shows why that matters. A trail page must hold a map, an elevation profile, statistics, photos, waypoints and tags without becoming cluttered, and search is split between a text box and a map. Data density is the main UI problem for a catalogue like this, and clean presentation is what keeps the per-trail metadata useful. On a phone screen the problem gets harder, because a map and an elevation profile compete for the same few inches. The read-only social layer at least keeps the mobile app focused on recording and navigation.

Performance can only be judged at the design level. On self-hosted setups, server responsiveness depends on the host’s hardware and the administrator’s upkeep, not on openwanderer. On the phone, background GPS recording carries the battery cost common to every tracker, and offline map regions use storage space in exchange for independence from signal. The deferred-upload design is the right choice, because it keeps the app useful in the places a trail app most needs to work.

Android is the platform covered here, and distribution is the first quirk. The app ships through Google Play’s open testing track, so installing it means joining a beta program instead of installing from a standard store listing.

Touch input suits the app’s job of recording and following a route. Editing lists, writing comments and logging summits stay on the web, since those features are read-only on mobile. Pricing is the same everywhere: wanderer has no paywall and no subscription. Compatibility depends on the server. The app needs a compatible instance version, so Android users on an older community server should expect no connection until it is upgraded.

wanderer handles the catalogue well. The import breadth, rich trail records, solid search, lists and summit logs are built for a collection that grows over years. Federation and open-format export mean that collection never belongs to anyone but its owner. Offering that at no cost makes the case for self-hosters, though it does not erase the app’s limits.

The Android app is what holds the score back. Offline maps, background recording and automatic upload make a sound field toolkit. But the read-only social and curation features, the missing voice guidance and rerouting, and the developers’ own warning against using it as the only navigation tool keep it a companion, not a primary app. Add the upkeep that self-hosting demands and a community still in its early days, and the audience narrows to people who value control over convenience. For that audience it is a reasonable recommendation, with a backup navigation tool in the pack. Everyone else should watch the beta’s progress.