Google Trips

» see google.com/trips as it lived, on the wayback machine

~ the obituary ~

google trips was for the kind of traveler i was not. in 2016 i was in ankara, working on edge ai stuff, and the trips i took were either drives to the coast or short business hops where you do not really need a day plan. the trips app was built around the assumption that you were on a multi-day vacation in a foreign capital and wanted a hand-held assistant that pulled your flight booking out of gmail.

it launched on september 19 2016 as android and ios apps. the pitch was that google could turn your gmail reservations into a trip itinerary automatically, then layer city guides for two hundred destinations on top. you opened it, it knew you were going to lisbon next week, it had a day-by-day breakdown ready. for the right user this was something close to magic. for me the magic part was always the empty screen, because most of my actual travel was to places google had not written guides for.

google killed the standalone app on august 5 2019 and folded the feature set into the regular google travel web product at google.com/travel. the public reasoning was that mobile users could use the responsive web version instead. that worked for the city-guide layer. the offline-itinerary part was the thing the app had been doing that the web version could not really replicate, and google did not seem to think that mattered.

~ the case file ~

~ how it landed ~

trips arrived in the second wave of google productivity apps, after inbox by gmail and the allo messenger. the era's pitch was that google was going to put a clever little app on every consumer surface where it might add value. travel was the defensible vertical because google already owned hotel and flight search through itineraries pulled from gmail. the first reviews were warm. tech bloggers liked the offline mode and the way the app gathered reservations without manual entry.

the catch was always that the value of the app scaled with how much travel you did to cities that google had bothered to map deeply. paris, tokyo, new york: yes. ankara, izmir, denizli: no. the two-hundred-city number was generous in count and narrow in coverage. anyone outside the western-cosmopolitan tourist circuit found the app's day-plans thinning out fast.

~ what really happened ~

the killedbygoogle.com pattern showed up cleanly here. an early product, a couple of years of refinement, then a quiet sunset to a web-only version that drops half the original functionality. google trips became google travel, which is a search-results-bar feature inside google flights and google hotels rather than a planning app. anyone who had used the standalone app for the offline maps and the consolidated itinerary view got pushed onto a website that needed signal to work and that was missing the offline pieces entirely.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »