← Back to selected work
Case Study 03 / Google Maps AR Navigation — Research & Concept Development

When a map meets the street.

How can navigation help people understand not just where to go, but which direction to face? This case study explores research and concept development around augmented-reality walking navigation, focusing on orientation, clarity and the connection between digital maps and physical surroundings.

Portfolio reconstruction · Concept exploration
Focus
Spatial UX / AR navigation
Role
UX research and concept development, as part of a team
Context
Professional experience-design work at Infosys
Product reference
Google Maps Live View
Status
Research and concept-development case study
01 / The challenge Design problem under investigation · Not a quantified finding

A route is not a sense of direction.

Following a route on a 2D map can require people to mentally translate a screen into their immediate surroundings. In unfamiliar places, understanding the correct heading, finding useful landmarks and recognising the next turn may be as important as the route itself.

Illustration of the design problem. Portfolio reconstruction · Concept exploration
  1. Q1

    How might a navigation experience help people establish their initial orientation?

  2. Q2

    What makes a directional cue understandable without overloading the camera view?

  3. Q3

    When should AR guidance complement, rather than replace, a conventional map?

  4. Q4

    What happens when environmental conditions or location accuracy interfere?

02 / My role & collaboration Team-based work

One contributor in a design team.

As part of an experience-design team, I contributed to research, competitive analysis, journey mapping, information architecture, wireframing, concept exploration and presentations. The work examined how AR navigation could communicate spatial information more clearly. The following materials are portfolio reconstructions of the design thinking and should not be confused with internal Google deliverables.

My contributions, within the team

  • UX research & research framing
  • Competitive analysis
  • Journey mapping
  • Information architecture
  • Wireframing
  • Concept development
  • Presentations

Not part of my role or this case study: engineering or AR development, AI work, production implementation, independent research leadership or product ownership.

03 / Research & competitive review Design investigation · No study results reported

Looking closely at how people orient.

The UX review treated walking navigation as a design investigation. What follows separates three different kinds of material: areas the team examined, functionality Google has documented publicly, and hypotheses that would still need testing.

Team research & analysis

Areas I helped examine

  • Digital map orientation versus physical orientation
  • Search and destination-selection interactions
  • Clutter in the navigation interface
  • AR directional cues and possible alignment difficulties
  • Environmental visibility and battery-use considerations
  • Discoverability of navigation modes

Topics of investigation. No respondent numbers, test rounds or results are reported here.

Public product context

Documented by Google

  • Google Maps Live View is the existing AR walking-navigation feature this work refers to, described in Google's 2020 blog post and Maps help.
  • In 2022, Google published an overview of Live View alongside the ARCore Geospatial API.
  • Google publishes developer documentation for the ARCore Geospatial API.

Summarised from Google's public pages listed under References. Not internal research or my own work.

Untested hypotheses

What would need testing

  • Confirming the starting heading before the first instruction may reduce wrong-way starts.
  • Fewer, clearer cues may be easier to read than several overlays at once.
  • A visible way back to the standard map may help when AR guidance is unavailable or uncertain.
  • Short, occasional camera use may suit walking better than continuous screen attention.

Hypotheses only. Not validated by user testing.

Navigation landscape: interaction patterns reviewed

PatternHelps withPossible difficulty
2D map with a location markerAn overview of the route and surroundingsTranslating the screen's orientation to the street
Step-by-step instruction listKnowing the next actionMatching street names and distances to what is visible
Heading indicatorSeeing which way the phone is facingUnderstanding the indicator at a glance, especially when it seems unsteady
AR camera overlayConnecting directions to the surroundingsScreen attention, visibility, battery use and alignment

Pattern-level design analysis, not a feature comparison of named products and not test results.

04 / Experience mapping Reconstructed artefacts · Not verbatim findings

Mapping uncertainty along the walk.

The persona, empathy map and journey map below are reconstructed design-thinking artefacts. They frame assumptions to explore and test; they are not research findings, participant data or copies of confidential documentation.

Scenario · Not a research participant

The first-time visitor

An illustrative scenario used to frame design decisions.

Situation
Walking from a station to an unfamiliar destination for the first time.
Goal
Set off in the right direction and arrive without second-guessing.
Habits
Checks the route before leaving; glances at the map rather than reading every step.
Constraints
One hand often busy, bright daylight on the screen, limited battery and a busy street to watch.
What might help
A clear first heading, recognisable cues and an easy way back to the map.

Uncertainty

  • Unsure which way to start walking
  • Unsure whether the position shown is accurate
  • Hesitates at complex junctions

Confidence

  • Recognisable landmarks offer reassurance
  • Confirmation at each turn helps
  • Seeing the route against the street reduces doubt

Navigation habits

  • Checks the overview before leaving
  • Turns the phone to match the street
  • Glances rather than reads

Potential frustrations

  • Walking the wrong way before noticing
  • Busy overlays while moving
  • Battery drain and screen glare
Illustrative empathy map · design assumptions, not research findings or participant quotes.

Journey map: four phases of a walk

  1. 01

    Establish location awareness

    Goal

    Understand where I am and which way I'm facing.

    Possible friction

    The map's orientation doesn't match the street; the position may be uncertain.

    Interactions

    Open the map; check the location marker and heading.

    Opportunities

    Make the heading explicit; point to a nearby visible cue.

  2. 02

    Search and select a destination

    Goal

    Find the right place quickly.

    Possible friction

    Similar-looking results; small targets while walking.

    Interactions

    Search, compare results, open destination details.

    Opportunities

    Distinct result details; easy confirmation of the chosen place.

  3. 03

    Start and follow AR walking guidance

    Goal

    Set off in the right direction and stay on track.

    Possible friction

    Finding the AR mode; aligning the camera; clutter; glare; battery use.

    Interactions

    Choose the walking route; enter AR guidance; follow cues; glance at the map.

    Opportunities

    Orientation step first; restrained cues; an easy switch back to the map.

  4. 04

    Reach and confirm the destination

    Goal

    Know I've arrived at the right place.

    Possible friction

    The entrance isn't obvious; the final metres feel ambiguous.

    Interactions

    See the arrival prompt; check destination details.

    Opportunities

    Clear arrival confirmation; an entrance cue; a simple return to the map.

Reconstructed journey map. Goals, friction and opportunities are design assumptions, not verbatim research findings.

05 / Information architecture & wireframes Portfolio reconstruction · Not Google production screens

From search to arrival, with a way back.

The conceptual route moves from search to arrival, but every step needs an exit: back to the map, to written instructions, or to standard guidance when AR isn't available. These are new portfolio reconstructions inspired by my original low-fidelity work, not recovered files or production screens.

  1. 01Map / Search
  2. 02Destination details
  3. 03Walking route
    • Check step-by-step instructions
  4. 04AR guidance entry
    • AR unavailable → continue on the standard map
  5. 05Directional guidance
    • Return to the map view
    • Check instructions
    • Location uncertain → map fallback
  6. 06Destination arrival
    • Return to the map
Main route Optional path Fallback path Portfolio reconstruction · Concept exploration

Low-fidelity wireframes

WF1 Destination search
WF2 Destination & route overview
WF3 Walking navigation / AR entry
WF4 AR camera guidance
WF5 Fallback to a standard map
WF6 Arrival confirmation

New low-fidelity reconstructions with placeholder content in brackets. Not original files and not Google production screens. Portfolio reconstruction · Concept exploration

06 / AR interface concepts Portfolio reconstruction · Concept exploration

Show less, orient sooner.

These original concept screens show interaction thinking, not a functioning AR engine. The street is illustrative; there are no real places, map tiles, Street View imagery or production interface assets.

C1

Orientation before instructions

The first screen only asks for a heading. Turn-by-turn detail waits until the person is facing the route.

C2

Clear directional arrows

One continuous cue on the ground, anchored to the turn, instead of several floating markers.

C3

Reduced-overlay hierarchy

The same moment with and without competing overlays: one cue and one line of text keep the street visible.

C4

Moving between AR and the map

The map stays one step away, so AR complements the overview instead of replacing it.

C5

A clear fallback

When guidance can't be trusted, the screen says so plainly and offers the standard map instead of a misleading arrow.

Portfolio reconstruction · Concept exploration. Illustrative street, invented layout and placeholder copy. Not a working AR feature or a production design.

Design principles

  1. P1

    Establish orientation before presenting complex instructions

  2. P2

    Prioritise legible guidance over visual clutter

  3. P3

    Provide a clear non-AR fallback

  4. P4

    Consider environmental conditions and location uncertainty

  5. P5

    Encourage safe, occasional camera use rather than constant screen attention

Principles that guided the concept exploration. They are design intentions, not results proven by user testing.

07 / Contribution & reflection Team-based artefacts · Not launched features

Less information, better timed.

Team research and concept artefacts I contributed to

  • Research framing
  • Competitive analysis
  • Journey maps
  • Information architecture
  • Wireframes
  • Concept explorations
  • Presentations

This work strengthened my ability to examine a product experience as a relationship between people, interfaces and their environment. The most useful design question was not simply how to display more information through AR, but when additional information helps someone make a confident decision — and when it becomes another source of friction.

08 / Evidence & attribution

Team contribution, independently reconstructed

This case study reflects my contribution to team-based UX research and concept development. Visual artefacts have been independently reconstructed for portfolio presentation. Google Maps Live View is referenced as the existing product context; this page does not claim sole ownership of Google features, a confirmed Google partnership, production implementation or verified numerical impact.

Public product references

These references explain public Google functionality. They are not evidence that I personally built Google Maps features or conducted internal Google research.