On November 9, source @elnarvideo posted a series of tweets on the X platform, reporting that Samsung’s first mixed reality headset, the Galaxy XR, suffers from optical design issues that cause noticeable eye strain and discomfort during use.
The user noted that when viewing distant objects in the virtual environment through the Galaxy XR, their eyes experienced significant fatigue and discomfort. In contrast, looking at nearby objects felt considerably more comfortable. The user speculated that the root cause lies in design trade-offs Samsung made in pursuit of a wider field of view (FOV).
It is believed that Samsung may have positioned the internal display closer to the lenses. While this approach enhances immersion, it has the side effect of shortening the focal plane—the distance at which the human eye naturally focuses most comfortably—from the industry norm of around 1.2 to 1.8 meters (4 to 6 feet) down to approximately 0.9 meters (3 feet). IT Home has included relevant screenshots as reference.
When the eyes are forced to focus on a physically near focal plane while simultaneously perceiving virtual objects that appear to be far away, a phenomenon known as vergence-accommodation conflict​ occurs. This is a well-documented cause of eye strain in VR devices.
To mitigate the discomfort caused by this issue, the user also observed that Samsung’s Android XR operating system, which powers the Galaxy XR, artificially limits the maximum placement distance of virtual windows to roughly 2.4 to 3 meters (8 to 10 feet). This software-based restriction serves as a compensatory measure to optimize the user experience.

Look for continuity without constant callbacks

A companion should use remembered context when it helps, not repeatedly announce that it remembers. Good continuity reduces the need for the user to restate important information and makes recurring activities easier to resume.

If every response references old history, personalization can feel forced rather than natural.

Check how the system handles a mistake

Correct a fact, reject a suggestion or change topic abruptly. The companion should repair the interaction and update the relevant state instead of arguing or repeating the same assumption later.

Evaluate whether the relationship remains user-led

Notifications, progression and premium features should support the user’s chosen interaction rather than manufacture urgency. Quiet hours, frequency controls and easy cancellation are practical signs that the product respects the user’s pace.

Compare richer media with the core conversation

Voice, images and video are valuable when they reinforce the same identity. If media quality is inconsistent or arrives too slowly, a simpler response may produce a better overall experience.

Test the product over more than one session

A first conversation can show personality, but long-term quality appears only after the system has accumulated memory, preferences and notifications. Return later, change a preference and see whether the companion adapts without losing its core identity.

Longitudinal testing also exposes repetition and stale context that a short demo cannot reveal.

Use controls as part of the quality test

Try the memory, notification, privacy and reset controls before you need them. A strong companion should make important settings understandable without forcing the user to delete the entire relationship to repair one problem.

The best experience becomes more relevant over time while remaining easy to correct.

A final long-term check

Repeat the same test after several days and after changing one setting. AI products accumulate memory, synchronization state and billing or permission history, so problems may appear only after the first-session novelty has passed.

The strongest products remain understandable as history grows: users can see what changed, correct the relevant state and continue without rebuilding the entire relationship.