RMS Interactive Maps

Redesigning the Map Booking Experience
Broken Experience
Clients uploaded a static JPG of their site layout. Staff manually drew rectangles over the image to mark bookable sites. A survey of 21 users revealed:
- 76% said the map experience was not mobile-friendly
- 57% said the map was hard to navigate
- 29% said filtering was too limited
- 29% said the experience was frustrating to use
Properties were churning. With no scalable infrastructure, every customer map was manual and inconsistent.
The question wasn't just how to fix the maps. It was about building a system that scaled across thousands of properties and worked on every device.
What the Research Revealed
Competitor analysis across 10 platforms found the same gap everywhere. Most offered interactive maps or booking integration. Rarely both. That was the opportunity.
The sharper insight came from problem framing. Guests choosing a site for a family or group holiday aren't just picking a location. They're managing the needs of multiple people.
Kids' play areas, quiet zones, proximity to amenities, sites next to friends. A poor map experience doesn't just frustrate. It creates stress, drives negative reviews, and reduces the likelihood of returning.
Six Improvement Identified
Built to Scale. Built to Last.
Worked with our frontend engineer to select the mapping stack. MapLibre and Maputnik. Open-source, fully customisable, no vendor lock-in.
One design rule established early: RMS owns the colour system, not the customer. Inheriting brand colours failed WCAG AA. Ticketmaster's seat map set the benchmark for colour and state at scale.
Seven interaction states designed and tested across zoom levels, devices, and property layouts. Two layouts A/B tested. Version A won, 9 out of 9.
Static JPG maps replaced with a fully interactive, mobile-first experience inside the RMS IBE. Real-time availability, filtering, site selection, and checkout, without leaving the map.
Shipped globally. Retained customers.
What was learned
Overriding customer brand colours was met with pushback. Proving it with accessibility data rather than design opinion was what moved it forward. Lead with evidence.I'd push earlier for conversion data tied directly to the maps feature. The retention story is real. It needs a number to become a compelling business case.














.avif)



