Turn the navigation arrival card into a last-100-metre handoff

[Medformatik]

Problem

Navigation currently recognizes arrival, but the destination often still requires a last-100-metre handoff: finding parking, remembering where the vehicle was left, locating the correct station/building entrance, and walking from the stopped vehicle to the actual destination.

Current state

• Arrival detection and mode-specific arrival cards exist.
• The ground card primarily shows “Arrived” and Done; transit adds destination/time context.
• Parking POI integrations, park-and-ride routing, walking routing, and stop/platform infrastructure exist independently.
• There is no arrival state machine connecting nearby parking, parked state, entrance selection, and a final walking leg.

Proposed solution

Turn the arrival card into a mode-aware handoff surface. For driving, offer nearby appropriate parking and an explicit “save parked location” action. When an entrance is known, offer a short walking route from the actual/saved vehicle position to that entrance or destination. Keep a simple Done flow for users who do not need assistance.

Acceptance criteria

• Arrival behavior is modeled as explicit states/events so reroutes, app restarts, GPS drift, and repeated arrival triggers are deterministic.
• Driving arrival can show a bounded, relevant set of nearby parking options with restrictions/availability provenance and routing detour.
• Saving parked location is opt-in, confirms the chosen/current position, associates a vehicle when available, and can be undone.
• The card resolves an appropriate destination/station entrance when infrastructure data exists, including accessibility requirements.
• A user can start a pedestrian route from actual or saved vehicle position to the entrance/final destination without rebuilding the original trip manually.
• Unknown entrances or unavailable walking routes degrade to destination coordinates and clear guidance.
• Transit/walking/cycling arrivals receive relevant actions without showing vehicle-only controls.
• Parking/entrance requests are bounded, cancellable, cached appropriately, and do not block the basic arrival UI.
• Offline behavior is defined for saved position, nearby cached POIs, and route availability.
• Exact location is not logged, shared, or retained as history; clearing parked state is immediate.
• UI is usable with one hand, screen readers, large text, and reduced motion.
• Tests cover GPS uncertainty, parking before/after the destination, multi-entrance stations, accessible entrance failure, restart, and Done/Stay behavior.

Alternatives considered

A single Done action is predictable but leaves common arrival tasks disconnected. Automatically saving parking or starting a walking route would collect data and surprise users.

Area

Navigation, parking, station entrances, personal vehicles, walking routing.

Dependencies

Integrates with station entrances (#298) and personal vehicles/parked state (#305), but should degrade gracefully before they are complete.