For now, let's head back down below. Our first train arrived early, just seconds after reaching the platform. Without adequate GPS reception, however, the app didn't even know we boarded until we resurfaced 10 minutes later in Times Square. Maps did provide a list of stops, which accurately reflected the on-train display (phew). After reaching Times Square, we decided to return to the office via bus. Unfortunately, Maps insisted that we ride the subway instead, refusing to provide door-to-door routing for any of the bus lines that would have enabled us to get home without losing GPS. The only option was to input a starting point too close to our destination for the subway to be practical, so we walked 20 blocks to catch the bus, which arrived two minutes early. Once we started moving, Navigation adjusted, swapping a bus arrival countdown for our destination stop, and an adjusted countdown. As we passed the second-to-last stop, our Nexus S 4G vibrated and displayed a "get off" warning -- so you'll know when to get off even if you're taking an unexpected snooze.
Once we hopped off the bus and made a turn off the bus route, the app switched to walking directions, which we followed for a few feet until we reached our destination. We imagine the same instructions would appear when riding other vehicles, such as trams and trains, though we couldn't test on the subway because of poor connectivity. Overall, Google Maps Transit Navigation (beta) worked very well, though we would have liked an option to choose to ride the bus instead of the subway (hint hint, Google!). We're especially excited about the growing availability of transit nav beyond New York City, and look forward to finding our destination without hassle on the next overseas adventure.