Back to journal

Changing the map should preserve the journey around it

On October 10, I completed an implementation change across Seasonal.Work's map surfaces. The maps moved from the previous map stack to Google Maps, but replacing the background was only a small part of the task. People used those screens to move between locations, result lists and individual records. The change needed to preserve that journey rather than make a familiar feature behave like an unrelated new application.

A shared renderer supported the five affected surfaces, including the native web application and retained pages. Markers, record popups, locations sharing the same point, map/list switching and location search remained part of the acceptance checks. The map also needed a useful state while loading or unavailable. A blank region would leave the person guessing whether there were no results, the map had failed, or the application was still working.

The provider change also affected what the site needed to explain. Privacy and terms content disclosed the map requests and linked the relevant policies. That disclosure was part of the implementation, not evidence that every later operational decision had already been made. Production use still had its own release and provider prerequisites. Keeping those decisions separate helped avoid treating a completed interface as automatic permission to activate every service it could use.

The implementation was merged on October 10. The recorded checks exercised all five surfaces with fabricated records and the real map software, with desktop and emulated-touch coverage for the native jobs and candidate pages. The full local verification also passed for the candidate. These results establish the tested implementation, while production browser acceptance and physical-device behavior remained unverified. The release procedure retained a separate staged review before promotion, so merging the source was not itself a claim of live availability.

Reflection

A map is part of a search journey, not just a visual background. On Seasonal.Work, the useful acceptance question was whether the same records and actions remained understandable after changing the provider. Preserving those relationships, and explaining failure honestly, mattered as much as rendering the new map.