I · The brief
The destination had plenty worth seeing, but discovery was scattered across brochures, signs, social posts, and local knowledge. Visitors could arrive, miss half the good places, and still technically have followed the official information. The goal was to bring the destination into one web and mobile experience: searchable POIs, routes, live user context, directions, and notifications that could nudge people toward relevant places at the right moment.
II · What we built
- —A destination website for browsing points of interest, categories, routes, and practical visitor information.
- —A mobile app with live user location, nearby POI discovery, and map-based directions.
- —Push notifications for location-aware prompts, event reminders, and destination updates.
- —A POI management structure for categories, descriptions, images, coordinates, opening notes, and visibility rules.
- —A lightweight analytics layer for tracking discovery, direction starts, and visitor movement patterns without turning the whole thing into a surveillance goblin.
"Visitors stopped asking where to go next."
III · What changed
+42%
POI visits from app users
3.8×
more map direction starts
−61%
visitor questions at info points
IV · What we'd do differently
We'd define the POI taxonomy earlier. Everyone thinks they have 'places' until you ask whether a beach, museum, trail, event venue, viewpoint, and seasonal kiosk belong in the same model. They do not. They absolutely do not.