Define nearby by the trip you can make
A café a few blocks away is a different proposition on foot, on a bicycle or in a car. Crossings, entrances and one-way streets can change the practical journey. A target distance helps narrow a search, but it is not the same as the length of a usable route.
Start with the mode you will actually use. Then compare candidates within that choice. Switching to driving simply to make a distant candidate look quicker does not solve parking or access.
Walking is more than a straight line
For a walk, look at which side of the river, railway or large road the place occupies. Confirm the intended entrance if an appointment is inside a campus or large building. A map pin often identifies the place rather than the door you will use.
When directions are available, Nowhop can show the estimated journey from the chosen start. That is a useful comparison, not a guarantee of a step-free route, a quiet path or a particular pavement condition.
Cycling and driving need different checks
For cycling, consider where you will leave the bike and whether the destination is accessible from the route you intend to ride. For driving, include the practical gap between arrival nearby and reaching the venue. Neither detail should be hidden inside a supposedly exact number.
Apple’s Maps app and the public MapKit interfaces are separate products with different capabilities. A cycling option must not silently relabel a walking or driving estimate. If the requested mode cannot be resolved, treat the estimate as unavailable.
Keep the decision reversible
Try a closer candidate if the journey leaves too little margin. A selected place becomes an arrival-only Plan entry. It does not reserve parking, set a visit length or automatically plan your return home. Your later recorded movement stays independent of that intention.
These instructions describe the Nowhop development workflow, not a navigation certification. Apple’s MapKit documentation explains server-based directions, and its travel-time reference explains why actual conditions can differ.
Questions this guide answers
Is the target distance a guaranteed route distance?
No. A geographic search constraint and an actual journey answer different questions. Check the route estimate and the surroundings instead of assuming a straight-line radius is a walkable distance.
Can I compare all transport modes as equally accurate?
No. Availability depends on the requested service, region and mode. Missing information should stay missing; an estimate from another mode is not a substitute with a new label.
Will the chosen mode classify my recorded day?
No. Choosing a discovery mode does not prove how you later traveled. Recorded distance describes accepted movement; it is not automatically labeled as exercise, driving or cycling.
Can I search from a planned stop instead of my current position?
Yes. Check the starting place and departure time supplied by the Plan context, or set the intended start. A future appointment is not assumed to be where your phone is now.
What if the road journey exceeds my nearby preference?
The actual route can be longer than the search radius. The current flow discloses an unavailable estimate or a route outside that preference before an explicit Add anyway decision.
Sources & scope
Official pages reviewed for this guide on October 31, 2026. Features and availability can change; check the linked provider before choosing.
Nowhop behavior is based on our implementation specification. Public demos use samples. Read our editorial approach.
See how a day comes together.
Try the Nowhop preview ↗Sample data. No sign-up or location access.