Case study 04
Chrome XR
Rethinking tab management for Android XR's Home Space.
In short
- The problem
- Chrome in Android XR’s Home Space uses desktop-style tabs. Testers could not tell tabs apart when their icons looked alike, and felt as confined as on a desktop monitor.
- The insight
- Google keeps desktop tabbing so browsing continues from laptop to XR glasses, so the design had to stay familiar while fixing what hurt: tabs people could not tell apart and a space as confining as a monitor.
- The outcome
- Of three low-fidelity designs the third ranked highest. Its high-fidelity version kept website names visible at any tab count, with icons added for recognition, and was shown without a headset using a method developed in existing design software.
Note: Research project. Not affiliated with or developed in collaboration with Google.
Act I — Setup
Setup
One beauty of browsing the internet is the ability to be in multiple places at once; in a web browser, this means opening multiple tabs simultaneously.
There is a standard format for opening tabs on a PC, and a different format for opening multiple tabs on a mobile device. These design choices are due to the different screen sizes.
The new Google Extended Reality software, commonly referred to as Google XR, features two modes: Home Space and Full Space.
In Home Space, apps run side by side with other apps, allowing for multitasking, while in Full Space, the app takes centre stage, offering a more immersive experience.

The Home Space web browser utilises a tab management system similar to that found on desktop browsers.
This poses a challenge: a monitor screen is limited to a rectangle, but an XR view can have at least an accessible 90-degree semi-focusable view (without a head turn) and a full 360-degree view (with a head turn).
Although XR still uses a top panel to manage the tabs in Home Space, it doesn’t look visually appealing to have multiple tabs open, and the large unused space around it is obvious.

Act II — Research
Research
To better understand how other users perceive their tabbing experience in the web browser, I conducted research with two groups.
The first group has a VR device (Oculus Quest) and has experience with navigation tabs on a VR device, on a desktop and on a mobile device. I found this group through my previous Master’s programme at the Luca School of Arts in Belgium.
The other group doesn’t own a VR device. They are regular users, not into tech, but comfortable browsing in the Chrome browser on desktop and mobile.
Both groups like to open multiple tabs, especially when researching or working, and don’t close them until their work is done, which can take weeks or even months.
Below is the breakdown of their feedback.
Group 1: has a VR headset, plus desktop and mobile
- They feel a sense of claustrophobia: they would like to be free but still feel confined to a space similar to that of their desktop screen.
- They admit they can have multiple windows side by side (3 max), but it still doesn’t solve the issue of multiple tabs stacking on each other in the Chrome browser.
Group 2: desktop and mobile only
- They are unable to identify and differentiate which tab is which, especially when they have similar icons, unless they click on it to open the tab.
- They would like to see some of the titles of the tabs; most times they are cut off when there are too many tabs open, and grouping tabs doesn’t solve this.
Research questions
After the research, I was able to figure out the pain points of the users and the questions I am solving for:
The questions I am solving for
- How can I create a better tab management system for XR that helps users visualise all their open tabs?
- How can I reduce the claustrophobia that arises due to multiple tabs being open?
Challenges
The main reason Google chose that format is to integrate it into their existing platform. To be clearer, they want you to open Google Chrome on your laptop or mobile and continue browsing the same tab on the Google XR glasses without a hitch, which is why they chose to stick with the desktop tabbing system.
Designing a new tabbing system has to keep the same functionality as the hybrid method to keep the sync.
Methodology
How I framed the design
- User’s need. Defining what the users are expecting helped me better streamline the design considerations.
- Universal design. I had to take into consideration what the users are familiar with, for them to be able to navigate seamlessly without a learning curve.
- Tabbing history. I studied how people were tabbing, in terms of how many tabs people open at a time and how often people switch from one tab to another.
Act III — Explorations
Explorations
These are wireframes based on the research.



The designs
Here are the designs.



Act IV — Testing
Testing
I conducted another study with the same participants, in the same two groups. This time I asked them individually to rank their top two choices, giving the pros and cons of why each design might or might not work.
Test round 1
What I tested
Which of the three low-fidelity designs works best. Each person ranked their top two choices and gave the pros and cons.
What I heard
Out of the three low-fidelity prototypes:
Design 1: pros
- It shows a little part of the website thumbnails.
- It shows the name (URL) of the website being visited.
Design 1: cons
- You can only see five (5) tabs upfront, unless you scroll downwards.
- It will take a lot of space and can be visually hindering.
- The thumbnails can be a visual overload.
Design 2: pros
- It displays the website thumbnails clearly.
- You can easily know what each page contains.
Design 2: cons
- The name (URL) of the website is not visible.
- It will take a lot of space and can be visually hindering.
- The thumbnails can be a visual overload.
Design 3: pros
- It can contain a lot of tabs arranged in a vertical order without them overlapping.
- It shows the name (URL) of the websites visibly in each tab.
- It is clean and simple.
Design 3: cons
- It does not show the thumbnails of the site.
High-fidelity prototype
I built a high-fidelity prototype and then added other websites to see how it would hold up.


Final user test
At this point, I was mostly done with the design and decided to go for one final test with my test groups.
Test round 2
What I tested
How well integrated the design is with their familiar tabbing system.
What I heard
After testing, the user was able to have as many tabs as possible while still keeping the names of the websites visible at all times. And since Android’s design considerations are taken into account, the tabs can still be shown and expanded into multiple tabs, but I still needed to add icons to identify the brand names.
Not everyone likes reading, but seeing the icon helps recognition.
Act V — The Turn
The Turn
Although they understood the design, this is the feedback I was able to gather from them.
User feedback after the final test
- Not interactive enough.
- It looks flat.
- They don’t feel immersion.
Act VI — Final
Final
This time, I thought about how best to present an augmented reality application without using a VR headset.
I researched several methods, since most people haven’t done this before, and I had to develop a way to make it possible using existing design software.

Act VII — Reflection
Reflection
The discussions I had with users have made me realise that asking the right questions helps me understand their needs more quickly.
Also, you have to look beyond what the user is saying to understand what they meant, because most people are bad at communicating.
Thanks We extend our sincere gratitude to everyone who participated in the user research. Your valuable input played a pivotal role in guiding the design process.