Skip to main content
Why designing for AR glasses is completely different from designing for mobile phones.
- July 9, 2026
You sit at your desk in Surat.
You take your beautiful flat mobile app screen.
You copy it directly into a 3D spatial frame in Figma.
You put on your new AR glasses to test it.
It looks absolutely terrible.
Your neck hurts from looking around.
You feel slightly sick.
You realize your standard mobile design rules do not work here at all.
I know exactly how frustrating this feels.
You see your friend Hiren easily landing high paying AR projects while you struggle.
You are not a bad designer.
You are just using the wrong map for a brand new world.
In 2026 AR glasses are not just phones glued to your face.
They require a completely different human psychology.
How frustrating this feels.
You see your friend Hiren easily landing high paying AR projects while you struggle.
You are not a bad designer.
You are just using the wrong map for a brand new world.
In 2026 AR glasses are not just phones glued to your face.
They require a completely different human psychology.
Why spatial computing changes everything and how you can adapt today.
The physical world is your new background
On a mobile phone you control everything.
You give your Spotify app a solid dark background.
In AR glasses the background is the user's actual messy kitchen or a bright sunny street.
If you use standard flat colors your UI will completely vanish when the user looks at a bright window.
You must design dynamic glass materials that adapt to the real world lighting instantly.
Eyes and micro gestures replace the thumb
Think about scrolling through an Airbnb listing.
On a phone the user swipes their thumb rapidly.
In spatial computing forcing a user to raise their arm and swipe the empty air is a terrible idea.
Their arm will get completely exhausted in two minutes.
You must design for the eyes.
The user looks at a 3D room and does a tiny invisible finger pinch resting on their lap.
You design for minimal physical effort.
Depth replaces the standard back button
Look at a complex app liake Cred.
On a phone you use a back arrow to return to the home menu.
In AR you do not use back buttons.
You use physical depth.
When a payment is done the receipt pushes backward into space and fades away.
The main menu pulls forward closer to the user.
You are acting like an architect building a room instead of a painter drawing on a flat page.
Common Mistakes to Avoid
Designing for 3D space is dangerous if you keep your old mobile habits. Stop making these massive mistakes today.
Locking the interface to the face.
If your floating app perfectly follows the user's eyes everywhere they look they will feel trapped and sick. Always pin your app windows to the physical walls or tables in their room.
Using tiny mobile typography.
A simple 14px font works perfectly when the phone is in your hand. In AR that text might be floating three meters away across the room. You must use massive and thick typography.
Ignoring spatial audio.
When a user taps a glass phone screen they feel a physical vibration. When they pinch the empty air they feel nothing. You must design tiny spatial click sounds so their brain knows the button actually worked.
The Final Word
Leaving your safe flat mobile screens behind is scary.
But AR is the ultimate playground for UX designers in 2026.
Stop thinking about flat rectangles.
Start thinking about human bodies and physical rooms.
When you master spatial depth clients will pay you exactly what you ask for.
