roam POCKET TRAILS / FIELD NOTESVisit Pocket Trails ↗

INTERFACE-BASED FEEDBACK · SEPTEMBER 2026

A walk is never
quite the same twice.

Three fictional people, three ways Pocket Trails could fit—or clash with—their everyday explorations.

Three possible walks

Different rhythms, different thresholds for trust.

01SOUTH KOREA · 34

Hana Cho

Freelance subtitler

Likes architectural photography, keeps handwritten lists, and walks to clear her head after work.

Her use case

An evening walk to find one interesting café or independent shop nearby.

“The purpose is clear: walk, notice something, save it. I like the nearby categories and the gentle encouragement to take a detour.”

Likely friction

Keeping an iPhone unlocked with the page visible can feel demanding and hard on battery life.

Likely outcome

Uses it for occasional exploratory walks, but may avoid route recording unless it works more flexibly.

02UNITED STATES · 58

Darnell Price

Municipal records clerk

Enjoys amateur astronomy, uses maps mostly for directions, and is cautious about location sharing.

His use case

A simple record of a weekend walk and the places he passed.

“The distance, elapsed time, and found places are easy to understand. I appreciate knowing where nearby-place data comes from.”

Likely friction

He may hesitate at location access after learning coordinates travel through the app to a place-search service.

Likely outcome

Adds places manually; wants a plainer privacy explanation before starting a recorded walk.

03ITALY · 21

Lucía Ferretti

Mechanical engineering student

Builds small electronics projects, often switches between apps, and already saves recommendations in Google Maps.

Her use case

Collecting independent shops found while wandering between classes.

“The saved-places section fits how I already use Google Maps, and colored pins could make my lists feel personal.”

Likely friction

Moving to Google Maps, copying a link, returning, and previewing it makes saving a place feel like several separate jobs.

Likely outcome

Likes the idea but may return to Google Maps alone unless saving becomes quicker.

Names, biographies, use cases, and quotations on this page are fictional.

WHAT EMERGES ACROSS ALL THREE

Curiosity is easy.
Confidence takes more work.

Pocket Trails is likely to feel inviting for small local explorations. The questions start when someone considers recording, sharing, or keeping what they find.

  1. 01

    Make tracking expectations unmistakable

    The visible experience says route recording needs an unlocked phone and an open page. Explain the practical consequence before a user begins.

  2. 02

    Make location data easy to understand

    Nearby searches use coordinates and an outside place-data service. A short, plain-language explanation can help cautious users decide.

  3. 03

    Reduce the distance between discovery and saving

    Google Maps link copying may interrupt the feeling of a spontaneous find. Streamlining that handoff could help habitual map users.

  4. 04

    Give memories a clear home

    The interface says journeys and saved places remain in the current browser. Users who value their records may look for a preservation path.

What was reviewed

Observed on screen

Location discovery, walk-start messaging, nearby category filters, manual place entry, journeys, saved places, Google Maps link guidance, and browser-local storage notices.

Not verified

No code inspection, location access, route recording, external map search, saving, or deletion. Existing browser-local records were not changed. Visible controls do not prove a feature’s complete behavior.