Graduate studio · 2025

Navi

Connecting visitors to New York City's local heartbeat.

Navi cover
Problem
NYC tourism defaults to top-ten checklists that skip the neighborhoods and people who make the city.
Role
UI/UX Designer
Timeline
January 2025 – June 2025
Tools
Figma, research
Outcome
78% of concept-test participants preferred neighborhood-led recommendations over generic top-ten lists

Key moves

  • Mapped tourist density across Manhattan to find where the checklists cluster.
  • Ran three user groups and six platforms through one heuristic evaluation.
  • Turned the research into a neighborhood-participation framework.
The full breakdown ↓

The concept: a regenerative travel platform for New York City

Connecting visitors to neighborhood-level experiences returns value to the communities they visit.

New York City sees over 60 million visitors each year. Most go to the same ten places. Meanwhile, local businesses outside those corridors struggle for visibility, and residents absorb the side effects of concentrated foot traffic.

Navi was designed to change that dynamic by connecting visitors to neighborhood-level experiences that return value to the communities they visit.

The first idea was a Manhattan heatmap

Mapping tourist density showed where the checklists cluster and where neighborhoods get skipped.

Before any of the user interviews, the first move was visual. Tourists overload a handful of spots, and the patterns are easy to picture: the swaths of people taking photos in front of the Brooklyn Bridge in Dumbo, the perpetual crush around Times Square. If a routing layer could see this imbalance in real time, the thinking went, it could steer visitors toward neighborhoods that get less attention.

Select a neighborhood to see how that early concept worked. Regions represent narrative emphasis, not live geo analytics. This is the prototype that would have shipped on day one. The research pushed back.

The instinct felt right, and also a little like a bandaid. Routing tourists somewhere quieter still lets them visit that place the same shallow way. So before committing to redirection as the lever, the next step was talking to the people who would actually use the thing.

Select from the list to preview how Learn would frame each of 12 neighborhoods.

Surveying three user groups, auditing six platforms

Residents did not want fewer tourists. They wanted visitors who engage more intentionally.

We audited six travel platforms and ran a heuristic evaluation of Airbnb using Nielsen's ten usability heuristics. Most tools were either transactional or editorial, but few connected discovery to community impact.

We then surveyed tourism professionals, local business owners, and long-time residents. Residents provided the richest dataset and most strongly shaped the personas.

Early on, the team considered a heatmap solution to reroute tourists away from congestion. The research reframed the problem, and it wasn't about volume.

Guest Favorite label overuse

The designation appeared on nearly every listing we reviewed, with no consistent criteria visible to the evaluator, eroding trust in a signal meant to shortcut decisions.

Minimal family & accessibility filters

Kid-friendly and accessibility-specific filters were thin. A crib amenity was often the only family-facing signal, leaving group planners without meaningful constraints.

Visual clutter and repetitive listings

Grid layouts offered minimal differentiation between stays. Similar photography and copy patterns created decision fatigue before a traveler could compare neighborhood context.

What the data said

The research pointed to intentional participation, not more destinations.

Residents consistently favored hidden gems over tourist traps and aligned with community-driven travel models.

Major concerns included overcrowding, rising local costs, and the loss of neighborhood authenticity. Participants were open to AI personalization only when it remained subtle and transparent.

Highlights from 14 survey responses: Reimagining NYC Tourism: A More Meaningful & Sustainable Experience (resident survey).

71%
concerned about overcrowding and over-tourism
50%
concerned about lack of authentic experiences

From research to framework

Three personas fed a Learn, Plan, Go structure that journey mapping validated.

Three personas emerged: Cain (group planner), Ororo (newcomer needing context), and Selina (commuter needing precision filters).

Given semester time constraints and no engineering handoff, the team focused on a coherent concept with real neighborhoods, realistic pricing, and clear user pathways.

The resulting framework was Learn, Plan, Go:

  • Learn surfaces local context.
  • Plan helps users compare and organize.
  • Go converts intent into bookings.

Journey mapping validated the structure across all three personas.

Building a system that reflects the New York state of mind

Every design decision linked back to research findings or persona needs.

Jost was selected for display typography to echo urban wayfinding cues. Orange became the primary accent to differentiate Navi from category defaults. Paired with Lato and a 4px spacing system, the UI remains readable and consistent across breakpoints.

The full system lives as a running component library, with the brand primitives, the semantic aliases, every interactive variant, and a live playground for flipping props. See the Navi design system. The components are also assembled into a working booking flow. Open the demo.

Editorial homepage slice

Plan a trip that gives back

Locally ownedNature first

Weekend in Harlem

Jazz history, local bakeries, and a sunset walk through St. Nicholas Park.

Chinatown food crawl

Dim sum counters and tea shops curated by residents, not star ratings.

LES art walk

Gallery openings and community murals, timed for quieter weekday mornings.

See it in product

Every screen in this section is pulled from the running build, not mocked up for the page.

The Navi system runs as a real, interactive product, not a static screenshot. Browse the feed, search a neighborhood on the map, open a host and try a booking. Everything is assembled from the components catalogued on the system page, which means the system shows up in the product the way it was meant to.

mylesdesignsthings.com/work/navi/demo

What Navi proved and where it goes next

Spreading tourists out was never going to change how they visit. Concept testing backed the deeper move.

What started as a heatmap turned out to be solving the wrong problem. Spreading tourists out doesn't change how shallow the visit is. Navi came from designing for the connection between visitors and the neighborhoods they're in.

Next opportunities include deeper neighborhood pages within Learn (surfacing history, local voices, and seasonal rhythms), richer collaborative planning tools for group travelers, and onboarding paths for local hosts and businesses to list their own experiences.

In concept testing, 78% preferred neighborhood-led recommendations over generic top-ten lists. That number is what Navi proved: community-centered travel holds up when the recommendations carry local context.

More work