40 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.

   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

2. 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.

   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

3. [Map Custom component] - satellite map texture option

   Add satellite map texture option to the map custom component additionally to the default texture https://developers.snap.com/lens-studio/features/location-ar/map-component

   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

4. Joost van Schaik

   Preprocessor directives, like the #ifdef in C#. This would enable quick changes between configurations and would be very useful if you write code that can be used both for SnapChat AND Spectacles, not to mention a future with multiple (generations of devices).

   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

5. Joost van Schaik

   Being able to write unit and run those in the editor. The test code should not be deployed with production code on Spectacles

   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

6. Joost van Schaik

   Being able to place breakpoints in the code and being able to evaluate variables at and state at that point. As in every popular dev environment

   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

7. UI development on Spectacles: friction points and feature requests

   UI remains one of the most time-consuming parts of the Spectacles AR development workflow, and I suspect we're all hitting the same walls in parallel and coming up with bespoke solutions for our respective use cases.

   I'd like to use this thread to surface those friction points collectively so we can hand the Spectacles team focused, granular feedback.

   To get the conversation started, the recurring gap I keep running into is the absence of a spatial equivalent of HTML and CSS, which is to say no declarative layout, no constraint solver, and limited runtime introspection.

   Coding agents help with the generation side of UI work, but that doesn't take you all the way to a coherent user flow, so the orchestration work still falls back on the developer.

   Those challenges are what prompted me to start releasing small open-source pieces addressing particular pain points. The first drop is a text reflow utility: https://github.com/a-sumo/spatial-flex/tree/main/packages/text-reflow

   To keep things actionable, a few suggested buckets to drop into:

   1. Layout and constraints: what's hardest to express? (centering, fitting text in a box, responsive sizing, anchoring)

   2. Runtime introspection: how are you inspecting instantiated UI today?

   3. Live preview and testing: how do you verify the user experience matches your specification?

   UI remains one of the most time-consuming parts of the Spectacles AR development workflow, and I suspect we're all hitting the same walls in parallel and coming up with bespoke solutions for our respective use cases.

   I'd like to use this thread to surface those friction points collectively so we can hand the Spectacles team focused, granular feedback.

   To get the conversation started, the recurring gap I keep running into is the absence of a spatial equivalent of HTML and CSS, which is to say no declarative layout, no constraint solver, and limited runtime introspection.

   Coding agents help with the… 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  ·  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

8. Table of what permissions are allowed together

   I would like to easily be able to visualize which permissions are allowed to exist together. This might exist already and I'm not aware of it. Could even be a calculator or something

   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

9. 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

   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  ·  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

10. Microphone not working on Spectacles with RemoteServiceGateway & ASR Module

    I am unable to get my lens to detect any microphone recording even though it works perfectly on Lens Studio.

    What I did:

    -Create a new project with Spectacles base template

    -Import remote service gateway

    -Use example for any AI service

    -Test on Lens Studio to ensure it work

    -Push to Spectacles to test again to find it not working

    -Create a ASRExample script from https://developers.snap.com/spectacles/about-spectacles-features/apis/asr-module

    -Test ASR on Spectacles and find it not working even though it works on Lens Studio

    -To ensure my microphone is not damage, I also tried the Imagine together lens and is able to use my voice to generate 3D objects

    Here is the project file I used: https://drive.google.com/file/d/1s_L9ou4LWDv9879aI3J3VLyURC0hedNB/view?usp=sharing

    Both my Spectacles OS and mobile app are on the latest version.
    I am using V5.15.4 for Lens Studio.
    My extended permissions is also enabled in Developer settings.

    I am unable to get my lens to detect any microphone recording even though it works perfectly on Lens Studio.

    What I did:

    -Create a new project with Spectacles base template

    -Import remote service gateway

    -Use example for any AI service

    -Test on Lens Studio to ensure it work

    -Push to Spectacles to test again to find it not working

    -Create a ASRExample script from https://developers.snap.com/spectacles/about-spectacles-features/apis/asr-module

    -Test ASR on Spectacles and find it not working even though it works on Lens Studio

    -To ensure my microphone is not damage, I also tried the Imagine together lens and is able to… 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

11. 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

    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

    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

12. 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

    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

    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

13. Video Capture mode

    It could be great to have a raw capture mode with the screen "off". Even if it's a use case that we see more on other pair of glasses without screen, it could also be great to have an easy way to record video without the screen on with nothing displayed that dont enable to see in dark (laser tag for example). We also need to ensure that the power button click re-enable the screen normaly.

    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

    under review  ·  0 comments  ·  Hardware / Ergonomics: (Fit, battery life, display brightness, audio)  ·  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. 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.

    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

    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.

15. Webview custom js/css

    Enable injecting custom javascript/css.

    Also allow for direct communication between the lens and the webview

    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

    under review  ·  0 comments  ·  Other  ·  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. Networking: Socket TCP/UDP

    Enable Raw socket TCP/UDP.

    This way we can also host directly a web server or even a websocket server directly on the specs.

    Or send/receive broadcast messages with UDP.

    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

    planned  ·  0 comments  ·  Other  ·  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. Webview + Spectacles feature requests

    Access to WebView audio volume; Access to the overall Lens audio mix; Access to Spectacles global audio level; ASR accepting audio inputs other than the microphone For example: WebView audio or the Lens global audio mix, enabling subtitles, transcription, or analysis for external media; YouTube Iframe support in WebView This would unlock many legitimate use cases for curated content, live streams, and educational experiences.

    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

    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

18. Setting Playback Position for AudioComponent Scripting API (seek() or play() offset)

    Can we get a way to seek within audio? Possible solutions: audioComponent.seek(timeInSeconds) or audioComponent.play(loops, startTimeOffset)

    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. Audio Output Support for Spectacles via BLE

    Afaik Spectacles doesn’t support streaming audio to external speakers even if there’s Bluetooth support on board. Is this something really not there ? or planned for future releases ? Would really appreciate the native ability to connect external speakers as this would enable a wide range of musical applications where I can control and make music in Lens and play it out loud.

    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

    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

20. We need a way to create dummy / spoof locations and places for the Places and geolocation APIs

    Developing location based apps in Lens Studio is a huge pain because there doesn't seem to be a way to really test the Places, Maps, etc APIs in Lens Studio since you need to be running on device to get real data. It would be cool if somehow each Specsd preview environment also had fake location / places / maps data associated with it that the API calls would get when making requests--or even a new type Specs preview window environment that is just basically a 3D view into the Map data--sort of Streetview-esque. So you can test outdoor navigation style Lens in Lens Studio using simulated world views / data.

    Developing location based apps in Lens Studio is a huge pain because there doesn't seem to be a way to really test the Places, Maps, etc APIs in Lens Studio since you need to be running on device to get real data. It would be cool if somehow each Specsd preview environment also had fake location / places / maps data associated with it that the API calls would get when making requests--or even a new type Specs preview window environment that is just basically a 3D view into the Map data--sort of Streetview-esque. So you can test outdoor navigation… 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

    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