Recently I had to incorporate Google map functionality on list of contact cards. I though it would be interesting to outline a decision map of what went into the design and development.
My first thought for the map functionality was to embed the map alongside the contact. This was quickly discounted since we had too many contacts on the same page (with a possibility of infinite scroll in the future). Although I could lazily load maps, one too many map requests did not make a lot of sense when all the user wanted did was to search and open a specific contact.
That made me transfer the map component to a popup (aka a detail) view.
The next problem was to embed the maps, which was easily done with Google API calls. However, the client organization “anticipated” many such API requests going out and, hence, exceeding the free API limit.
From experience with similar companies, this was not quite a common problem but the organization persisted on the requirement. More over, we also expected users to interact with the map for directions in specific use cases. Considering these factors, the popup to the actual Google Maps was perceived to be better and more user friendly.
I changed the design to a simple hard-coded map image that takes user to the actual Google map with focus on the address. The component uses Vue and Vuetify.
- Create a new field to hold latitude and longitude. Note to self to populate that whenever user selects address from a map
- Use latitude/longitude or the actual address to create the URL string. Open URL in new tab/window
The Vue component is simple -