Design: make favorite routes feel reliable during refresh and cache updates

[github-world192]

Problem

Favorite routes use cached route names and background refreshes. Without clear freshness indicators, users may not know whether they are seeing live arrivals, cached placeholders, or stale data.

Product design direction

Add lightweight confidence cues to favorite routes:

• Show last updated near the route section.
• Use a compact refreshing indicator that does not disrupt row layout.
• Distinguish placeholder, live, no data, and error states.
• Keep route cards/list items stable while only the arrival time changes.

Acceptance criteria

• Favorite route rows do not change size or order unexpectedly during background refresh.
• Cached placeholders are visually distinct from live arrival estimates.
• The user can see when favorite route data was last updated.
• Failed refreshes preserve prior useful data and show a subtle retry/error affordance.
• Long route names fit on mobile without overlapping arrival badges.

Senior design advice

For commute tools, perceived reliability matters as much as raw speed. A small freshness label and stable row behavior will reduce anxiety more than adding more animation.