54 results found

1. Improved Media Export

   Improved Media Export

   Currently getting captures off Spectacles is quite an annoying task. Frequently now when transferring the captures to the mobile app a very small amount actually succeeds in transferring, and when they do the transfer speed is slow, especially when transferring a large amount. It would be great to have some option to transfer over cable, potentially from within LS.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Spectacles App: (Pairing, media export, settings)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable Advanced Spatial Intelligence: Raw Mesh Access & Semantic Understanding

   Summary:
   Requesting an expansion of the WorldMesh API to allow for programmatic access to raw geometric vertex/index buffers and high-level semantic scene classification.

   Problem:
   While the current WorldMesh and HitTest APIs are excellent for visual occlusion and simple placement, they remain "black boxes" for advanced spatial reasoning. Specifically, we cannot programmatically access the raw vertex data to generate custom pathfinding (NavMesh) or perform geometric analysis (e.g., identifying surfaces for "Cover Finding"). Furthermore, semantic classification is currently limited to specific hit-test results; we need a more holistic way to query the scene's composition.

   Proposed Solution:
   -Raw Mesh Data Access: Provide an API to extract vertex and index buffers from the WorldMesh resource. Ideally, this should be delivered as a stream or via a "chunked" event system to maintain performance as the mesh refines in real-time.

   -Expanded Semantic Scene Graph: Provide a structured API to query the scene’s semantic layout (e.g., a list of all identified "Table," "Floor," or "Wall" objects within the camera frustum or radius) rather than relying solely on individual point-in-space hit tests.

   -Spatial Metadata: Expose geometric properties of these semantic objects (bounding volumes, orientation, and surface normals) to allow for sophisticated tactical AI, such as identifying valid cover positions or navigable space for agents.

   Impact:
   This would enable the next generation of "Spatial AI" experiences on Spectacles. Developers would be able to build intelligent agents that treat the user's home as a truly interactive, persistent, and "aware" environment, moving beyond simple overlays to meaningful mixed-reality game mechanics like tactical stealth and pathfinding-based navigation.

   Summary:
   Requesting an expansion of the WorldMesh API to allow for programmatic access to raw geometric vertex/index buffers and high-level semantic scene classification.

   Problem:
   While the current WorldMesh and HitTest APIs are excellent for visual occlusion and simple placement, they remain "black boxes" for advanced spatial reasoning. Specifically, we cannot programmatically access the raw vertex data to generate custom pathfinding (NavMesh) or perform geometric analysis (e.g., identifying surfaces for "Cover Finding"). Furthermore, semantic classification is currently limited to specific hit-test results; we need a more holistic way to query the scene's composition.

   Proposed Solution:
   -Raw Mesh Data Access: Provide an… more

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Spectacles App: (Pairing, media export, settings)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Making Specs more inclusive and usable

   I haven't tried the new version of Specs that was just launched, so I'm not sure if some of these features are already in the pipeline or implemented, but this came up in a discussion after Meta Connect and I wanted to put it out there.

   A major piece of feedback from the community on Specs is that the current inputs aren't very inclusive for people with disabilities. If someone has difficulty holding their hands up or keeping their hands in the camera frame for long, the OS itself doesn't have enough alternatives to make it usable for longer durations.

   I was speaking with Don Allen and he made a really good point like he doesn't have the strength to keep his hands up for long due to nerve damage. There should be native support for interaction beyond the camera frame, so a person can still use their glasses without that constraint. The neural wristband helped him to drag, scroll and select, which was useful, but personally I'm not a big fan of needing to wear extra bands or peripherals for basic input.

   After seeing Meta Connect, voice command felt very right at the operating system level. The OS itself should be navigable by voice - opening apps, moving between screens till you get into an experience - and then you can use hands if needed. Features like calling and phone notifications also feel essential for it to be a daily-use, personal pair of glasses.

   The other thing is that Lenses right now work as isolated apps without background access or parallel processing like widgets. It would help a lot if that was enabled.

   I really want to see Specs succeed because it's one of the only true AR glasses out there, but to stay ahead it needs to be more inclusive. All of this feels like a software upgrade, so I hope to see it soon in the consumer version of Specs as well, which would make a lot more sense on the device.

   I haven't tried the new version of Specs that was just launched, so I'm not sure if some of these features are already in the pipeline or implemented, but this came up in a discussion after Meta Connect and I wanted to put it out there.

   A major piece of feedback from the community on Specs is that the current inputs aren't very inclusive for people with disabilities. If someone has difficulty holding their hands up or keeping their hands in the camera frame for long, the OS itself doesn't have enough alternatives to make it usable for longer durations.

   … more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Prefab variants

   It would be very helpful to have something like Unity's prefab variants. I have now six nearly identical prefabs, and it's very annoying that I have to make any change I do 6 times.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Somebody give Matthew Hallberg a raise !!

   Matthew’s spatial Pokémon card prototype is exactly the kind of work that makes people genuinely excited about Specs. It is playful, instantly understandable, visually impressive and currently going krazyy viral.

   This is more than a cool demo. It shows how familiar physical objects can become portals into interactive spatial experiences. It communicates the potential of Specs better than a lengthy product presentation ever could.

   Please give Matthew a raise he deserves !!!

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. The new SPECS deserves a more modern spatial UI

   I really love the direction Specs is heading in, but I’m not sure whether I like the new UI redesign. The current home UI as seen in the launch feels visually dated. The crowded app grid, inconsistent icon styles and heavy panels make it feel closer to an old mobile launcher than an interface designed specifically for spatial computing 👀🫣

   I just did a quick AI assisted redesign concept which of course can be improved upon but feels much more modern imo.

   This is obviously just a visual concept, not something tested against the actual display limitations, field of view or performance constraints. I’m also not suggesting Specs should simply copy another spatial OS. It deserves its own interaction language and personality.
   The hardware is moving forward quickly. I’d love to see the system UI receive the same level of care.

   I really love the direction Specs is heading in, but I’m not sure whether I like the new UI redesign. The current home UI as seen in the launch feels visually dated. The crowded app grid, inconsistent icon styles and heavy panels make it feel closer to an old mobile launcher than an interface designed specifically for spatial computing 👀🫣

   I just did a quick AI assisted redesign concept which of course can be improved upon but feels much more modern imo.

   This is obviously just a visual concept, not something tested against the actual display limitations, field of view… more

   •  

   •  

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Spectator Mode: Exclude Layers & Capture Button

   Spectator Mode could become a really useful tool with a few tweaks.

   1. I'd love if one or multiple render layers could be set to be 'excluded from Spectator view', just to prevent UI or camera-parented objects showing up

   2. It needs a capture button in the app (making screen recordings is a pain)

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Spectacles App: (Pairing, media export, settings)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Prefab Renaming Sync

   Renaming a prefab in the Asset Browser does not update the name of newly created instances in the hierarchy. This creates tracking confusion for developers.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Guide SceneObjects

   Sometimes I use guide geometry to help with the layout of a scene, especially useful when building for real-life locations.

   It would be great if Lens Studio had the option to right-click a SceneObject and "Enable Guide", giving that object a little icon and making sure it is excluded when publishing. No assets on that SceneObject would count towards lens size, and they would be treated as if they were deleted if they were accidentally referenced by code.
   This would make it easier to have assets in a project purely for reference!

   (Inspired by After Effects' Guide layers which are not rendered.)

   Sometimes I use guide geometry to help with the layout of a scene, especially useful when building for real-life locations.

   It would be great if Lens Studio had the option to right-click a SceneObject and "Enable Guide", giving that object a little icon and making sure it is excluded when publishing. No assets on that SceneObject would count towards lens size, and they would be treated as if they were deleted if they were accidentally referenced by code.
   This would make it easier to have assets in a project purely for reference!

   (Inspired by After Effects' Guide layers which are… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Full Computer

    Glasses should not be inherently a 2nd citizen. We should be able to use it and develop for it freely, like any personal computer. So I suggest:

    • Spectacles app should be optional: anything the app can do, the glasses should be able to do it without the app (connect to wifi, etc...).

    • We should be able to use the glasses without any account, like an Android phone does not require a Google account or a mac/windows can only have local account just for security purpose. Accessing the snap store would be like Android, you need an account. But there should be ways to also sideload apps, even if it's more developer focused.

    • We should be able to access files, as it is an Android devices. (at least as a developer with adb)

    • I also know why everything is focused on Lens Studio to develop, but we should also be able to choose another way, even if features are not already there. For example, even on Apple Vision Pro that have a really closed ecosystem, we can still use Unity/Godot in addition to native swift. Supporting WebXR is already a very good thing, so thank you for that.

      • What would be also very awesome, is to support WebXR app as native ones (without all the unecessary things from the browser as it overheat very fast). Personaly, I would say that it is even better than supporting OpenXR.

    Glasses should not be inherently a 2nd citizen. We should be able to use it and develop for it freely, like any personal computer. So I suggest:

    • Spectacles app should be optional: anything the app can do, the glasses should be able to do it without the app (connect to wifi, etc...).

    • We should be able to use the glasses without any account, like an Android phone does not require a Google account or a mac/windows can only have local account just for security purpose. Accessing the snap store would be like Android, you need an account. But there should… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. System keyboard replacement for HID devices

    I build Scriber, a one-handed BLE chording controller with a companion virtual keyboard (ScriberEditor, open source: github.com/Altomand/ScriberEditor). Three related asks for SPECS system input:

    1. System-level BLE HID keyboards — pair once, type into any Lens or text field.

    2. Custom input methods — let developers register their own virtual keyboard as a replacement for the system keyboard on text fields (like Android/iOS third-party keyboards). When a physical input device is connected, the system on-screen keyboard shouldn't pop up.

    3. Tighter integration with the native Browser app — ability to pass field metadata (content type, current text) so a custom keyboard can adapt dynamically — different buttons or placement depending on the field, e.g. some keys changing to specific shortcuts when something is clicked. I'm happy to publish Scriber's virtual keyboard and accompanying code as an Asset Library package so the team has a concrete reference to integrate and test against.

    Context: raised in an r/Spectacles thread with nick-ross (https://www.reddit.com/r/Spectacles/comments/1vfekba/will_the_ble_api_come_out_of_experimental_status/). I'll be at the SPECS launch event and developer session on September 16–17 and can bring a Scriber unit for the product team to test, if that would help.

    I build Scriber, a one-handed BLE chording controller with a companion virtual keyboard (ScriberEditor, open source: github.com/Altomand/ScriberEditor). Three related asks for SPECS system input:

    1. System-level BLE HID keyboards — pair once, type into any Lens or text field.

    2. Custom input methods — let developers register their own virtual keyboard as a replacement for the system keyboard on text fields (like Android/iOS third-party keyboards). When a physical input device is connected, the system on-screen keyboard shouldn't pop up.

    3. Tighter integration with the native Browser app — ability to pass field metadata (content type, current text) so a custom keyboard can adapt… more

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. QR/Snapcode open url

    We should have something at the OS level triggerable in some way.

    Could be even better with an API callable from a lens.

    It could be also awesome to directly enter WebXR experiments.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    planned  ·  AdminShin Kang (Admin, Snap, Inc.) responded

    In our roadmap.

13. Component not yet awake error is too vague

    One of the more annoying errors is "Component not yet awake". Can we please get a script name and line where that happens?

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Let Specs function as a monitor and allow for wired screen mirroring.

    Looks like a lot of AR glasses competitors are seeing a lot of success marketing their products as “big digital screens” so people can plug in their gaming consoles or really just mirror any kind of screen to the glasses.

    It would be good for Specs to allow for that as well, straight out of the box.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Ability to copy files between projects

    Being able to copy files from one project to another with their .meta file without running into the stupid duplicate ID error. If Unity can do that, so should you be able to do that

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Endurance Mode

    I loved the (experimental) Endurance Mode that was on the 2021 device, it would be great to bring that back in some way!

    GPS locations could trigger a sleep or wake command on the device.
    This would be a great power saver for outdoors treasure hunt experiences or guided tours!

    (Reference: https://ar.snap.com/adapt-your-lenses)

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hardware / Ergonomics: (Fit, battery life, display brightness, audio)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. CLAD confused with @wearable

    CLAD gets confused with @wearable in API docs, one of the lenses I tried I wanted to add content to the ceiling. CLAD wanted to use world query but said I can’t test this in editor since it is marked as @wearable and therefore only works on SPECS. Instead it wrote an editor fallback, even though this does work in the editor.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. CLAD head-fixed

    CLAD a few times created head-fixed content, such as in game content and HUDs. HUD I can slightly understand, but even then there was no LERP applied, so it has that jitter look on device. No real reason for the game content to be headlocked, though.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. CLAD appearing to be crashed

    Frequently when using CLAD LS would appear to be crashed, I would get the spinning wheel on mac, but it hadn’t actually crashed, it was just doing something in the background. Some indication that CLAD / LEAF is currently interacting with the editor would be fantastic.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Lens Studio Integration: (Deploying to device, debugging tools, simulation, API limitations)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Support for Precision Stylus Input

    Requesting native support for high-precision stylus devices—such as the Logitech MX Ink or Muse—to be integrated with Snap Spectacles.
    Current interaction methods (hand tracking and gaze) are excellent for navigation but lack the precision required for professional spatial design, technical drawing, and complex 3D manipulation. Integrating a dedicated stylus would transform Spectacles into a robust tool for creative and technical workflows.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Snap OS / System UI: (Voice commands, hand tracking, Lens Explorer, notifications, connectivity)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating