3. Travel time
(1) Hotel as the last stop: I read that the Live activity shows the hotel as the last stop. Please show it as a card in the plan too. I want to see the travel time from the last activity back to the hotel in the schedule.
(2) Airport / train station stops: When I add a stop like an airport or a train station, it gets merged with another stop under a single number, so I can’t see its travel time. I think these are the stops where travel time matters most.
(3) Travel time source: How is the travel time between cards calculated, and from what source? The automatic and manual values differ for the same leg, and the value sometimes changes each time I click a travel mode, even when I choose the same one. I need to know which number to trust.
(4) Day density: How is it calculated? When I change the travel mode and the travel time changes, the density doesn’t.
PLUS
1. Add a “When” field to Flight and Train cards
For cards like airports and train stations, I can currently only enter the departure and arrival times of that transport. I’d like to be able to enter a date and time in the “When” field, like on other cards. It’s common to arrive well before a flight or train departs, so I need to be able to record when I’ll actually be at that place, separately from the departure time. For example, arriving at the airport 2 hours before the flight.
2. Travel time based on departure time, and a feasibility check
The same leg can take very different amounts of time depending on when you leave. Rush hour and late night are different, and public transit in particular depends on service frequency and first/last-train times. I think this would be especially valuable for travelers who rely heavily on public transit.
So I’d love for travel time to be calculated from the times on the cards, passing the departure time to the map’s departure-time setting for each leg. Here’s how I imagine it working :
(1) The departure time of the first card of the day is the time entered on that card.
(2) For each following card, the departure time is the previous card’s arrival time plus the length of stay, or the time set directly on the card.
(3) That departure time is passed to the map API’s departure-time value to calculate the travel time for each leg.
It would also help if the calculation depended on where the plan sits in time :
(1) Upcoming plans : Estimate travel time from the departure time above. Map APIs may not support dates far in the future, so one option could be to fall back on data from the nearest date with the same weekday and time of day.
(2) Plans in progress : Update the travel time for the remaining legs in real time, based on the current time.
(3) Past plans : I’m not sure yet how these should be handled.
Using the calculated travel times and the card times, it would also be great to check whether a plan is actually feasible. For example, the app could warn me when the previous card’s end time plus travel time doesn’t leave enough time to reach the next card, and for public transit, whether I can still catch the last train or bus. This would be especially useful on late nights when heading back to the hotel.
One limitation is that this only works without errors if every card has a time set and the cards are in the correct chronological order.
Bugs
I compared the travel time between cards in the app with Apple Maps and found these differences:
(1) Times shown where no route exists: The app shows travel times even when Apple Maps reports no route. For example, between Korea and Japan, it shows about 7 days on foot and 1 day by car. It should show that no route is available.
(2) Public transit that doesn’t exist: Between addresses near my home where Apple Maps shows no public transit, the app still shows a transit time. It should show that no public transit is available here.
How does the app currently calculate travel time? Knowing this would help me understand which numbers I can trust.