Case study
Google Trips
Personalized travel guide from Gmail. Automatic trip detection and organization with offline access.
Google Trips detected upcoming travel from Gmail and organized the details into one offline guide. I led the design for trip setup, day planning, and use without a reliable connection.
The trip assembled itself from information the user already had
Instead of asking people to enter flight numbers or hotel confirmations again, Google Trips used reservation email to create the trip. The interface then organized the useful details around the place and dates of travel.
Day Plans balanced automatic routing with manual control
The Day Plans feature used a wand control to generate a sightseeing route from location, opening hours, and historical popularity. A user could pin any stop worth keeping, then generate another route around that constraint.
The system handled route calculation. The user decided what belonged in the day.
The complete trip remained useful offline
International travel often begins with unreliable or expensive data. A downloaded trip kept its map, route, and reservation details available without a connection. The assistant did not depend on a live cloud session to remain useful.
One interaction model connected the underlying Google services
The product depended on reservation data, place information, and routing from different teams. I established the cross-product patterns that turned those inputs into one predictable trip structure instead of exposing the seams between services.