v2.3 and still no navigator UI?? what gives?
Since the navigator ui was introduced I liked it a lot. I used it while on the PTC and was 100% relived that i didn't have to have the ugly grey bar with limited slots for apps i actually use just hanging there all the time. Then an update (which was more a downgrade) removed it and brought the old universal menu back which sucked. Then i hear the navigator is replacing the universal menu permanently - Awesome! except its been several months and 3 version updates since then and my quest is STILL using the ugly menu that is useless to me because i cant put more than one app i actually use on it and its just an eye sore when i using 2d apps. WHY? i get your goofy rollout process but its been months and months and updates keep coming but somehow not updating the UI? theres not even an option to choose? what is this bs?
Design Audit: Why the Navigator UI is a Knock off Failure of Vision
To the Meta Design Team, you are making your device worse by trying to be someone else. Meta was the leader because you were the ones who actually figured out how to make standalone VR functional and accessible in the first place. For you to throw away the very leadership you built just to become a knock-off version of Apple is a total failure of vision. You didn’t need to reinvent the wheel, you just needed to polish it. Instead, you’ve scrapped a great, functional interface for a filtered version of the Vision Pro. By forcing the Navigator into a rigid, head locked position, you’ve sacrificed user sovereignty for a spatial look that you don't even have the eye tracking hardware to support on your current mainstream headsets. Even if your next device has that hardware, the millions of people using your hardware right now shouldn't be forced into a "look to lock" logic that makes the system feel broken. Taking away the ability to freely grab and park windows, forcing us to recenter our entire world just to move a menu is a massive UI/UX regression that makes the system feel less capable and more restrictive. This interface feels like it was designed by geeks who prioritize clean code and data structures over how a human being actually moves their hands and head in a room. Mark Zuckerberg started with a site that was nothing but white backgrounds and blue text a bland, sterile database and that same nerd logic has now infected the Quest. A nerd designs a menu based on where it’s easy for the code to sit; a designer or a real user needs it where their hand naturally wants to reach. Your current interface is the definition of mayonnaise tech: bland, sterile, and corporate. You finally made the Navigator transparent, but you stopped halfway. Transparency isn't just a style choice; it’s a mechanical need in a spatial environment. Why are the store, the menus, and the sub-folders still stuck in these solid gray and white blocks? Every single window should be transparent by default. This is the obvious direction for the medium, yet you're forcing us into light versus dark folders instead of just providing opacity sliders. Users need the ability to choose if they want to block the world out or let their room shine through. It is 2026, so being stuck with gray and white as our only options is a joke. A simple color wheel for the UI would allow for a green aura, a blue glow, or custom highlights for menus. A transparent green theme should be a simple slider adjustment, not a corporate mandate. You already had a winning format with the original Quest interface. You didn't need to scrap it; you just needed to make it transparent and give us the tools to move it. You need to restore the "grab to slide" logic so we can orbit windows 360 degrees and park them to our left or right without the system fighting us. Stop trying to look fashionable through imitation. You built your success on utility and being the original in the standalone space don't throw that away to be a second rate copy of a competitor. Give us back the original soul of the Quest, enhanced with the transparency and the customization that this technology actually demands.
Where is "Following Windows"?
I have wanted to be able to walk around my house watching YouTube with a floating window since I bought the Oculus Quest 1.... We are now on the Meta Quest 3, and I still can't achieve this goal. I have been told it was a feature, then they removed it..... Why on earth was this revoked from us before I got to use it? I would take a loan out in my own name for however much money you need to add this feature. I am so sick of walking around my house carrying my YouTube.... It's so annoying, and I want to know, am I the only person in the whole world who wants this but can't have it? I'm trying so hard to wait... I reached out to Meta in 2025 and was told it's coming. What am I missing that makes this feature so hard when all their UI pop-ups do this by default... I can't take no for an answer with this, and I want to be heard....
Feature Request / UX Discussion: Separate Immersive App Control UI From 2D Apps
``` I’d like to discuss an issue with how immersive apps interact with running 2D apps when switching contexts using the Meta button on Quest. The problem is not the immersive app itself, but the 2D control window that appears for immersive apps (the window with Resume, Close, and other controls). When this window is shown, it is treated like a normal 2D app, and its appearance often causes currently running 2D apps to be minimized, closed, or refreshed. This behavior makes multitasking unreliable and forces users into specific app-launch sequences just to avoid losing state in their 2D apps. Proposed Behavior Change The idea is that the immersive app control window should not behave like a standard 2D app and should not interfere with other running 2D apps. Specifically: - Showing the immersive app’s control window should not minimize, close, or replace existing 2D app windows - The immersive app control UI should exist in a separate system layer, not the same layer as user-launched 2D apps - Running 2D apps should remain exactly as they are when the immersive app control UI appears - Access to Resume, Close, and related immersive controls should be possible without disrupting active 2D workflows - Ideally, immersive app controls could be accessed via a dedicated icon, overlay, or system-level panel rather than a standard 2D window In short: Viewing or interacting with immersive app controls should not be treated as “launching a 2D app.” Why This Matters - Prevents active 2D apps from being kicked out or refreshed - Makes switching between immersive and 2D contexts predictable - Improves productivity and multitasking - Reduces frustration caused by forced app restarts - Allows immersive apps to coexist cleanly with 2D workflows This could be implemented as an optional setting or as a revised default behavior for immersive app control UI, without removing any existing functionality. I’m interested to hear if others experience the same issue and whether separating immersive app controls from the 2D app system would improve overall usability. ```
Question about Meta UI and returning to app
Hello, I am reaching out on behalf of one of our clients, who has reported the following: While running our application, their users may occasionally press the Meta button, which invokes the Meta UI and temporarily makes it so they cannot interact with our application until the Meta UI is closed out of. This part makes perfect sense. However, the issue is that they have reported difficulty in closing out the Meta UI and returning back to our application. Normally, users can either press the Meta button again (or press the 'Resume' button while the Meta UI is overlayed) to return back to the application. In our client's case, they state that they have to press the Meta button / press the 'Resume' button multiple times before the Meta UI finally responds to the action and closes out, returning to the application. In their troubleshooting, they could not find any consistent pattern that would indicate a condition that triggers this. For instance: They are using Quest 3 headsets Some of them are on Shared Mode or Kiosk Mode, while others are not Some of them are on an MDM solution while others are not The controllers do not have any noticeable debris on them and are regularly cleaned with approved electronic sanitization products (i.e. low moisture wipes and set to dry in a UV cart, not using any sprays) The controller batteries are also regularly charged before any session of our application is run Tracking frequency on controllers is set to 'auto' *Especially for the 2nd and 3rd point listed above about Shared/Kiosk Mode and MDM solution - it does not matter whether these headsets have these enabled. The issue occurs on headsets that have these enabled as well as those in which these are not applicable. Can you kindly please suggest additional troubleshooting suggestions that our client can try, as this issue is significantly impacting their use of the application? Thank you, and please let me know if there are additional details I can share.
How to manage ray interactions on multiple Unity Canvases on top of each other?
Hi, How do I manage disabling and enabling multiple world space canvases so the Ray interactions work properly, when the canvases are placed in front of each other? The UI canvases are default Unity world space canvases with ray interactions added with the quick actions described in this article: Add an Interaction with QuickActions | Oculus Developers The problem is that I have two worldspace canvases with ray interactions placed in front of each other, kinda like in layers. When I disable the canvas gameobject in front, the interactor cursor hits the disabled (invisible canvas) and does not properly pass through to hit the second canvas (which it should do). How can I ensure the cursor interacts with the first active/visible canvas and does not get captured by disabled ones?
