Developing for Spectacles within a mobile-first IDE creates unnecessary friction. Many mobile features are redundant or broken on the device, while essential Spectacles functions lack native integration.
Key Issues
• Feature Redundancy: Tools like Segmentation remain visible in the UI despite being unsupported, leading to developer confusion.
• Lack of Native Parity: "Device Tracking - Surface Mode" doesn't work natively for Spectacles; we shouldn't need a separate placement package for a core spatial feature.
• API Fragmentation: The shared API list is cluttered with mobile-only methods, making it difficult to identify Spectacles-compatible logic.
Proposed Solution
I am requesting a Spectacles-specific version of Lens Studio (or a dedicated "Native Specs Mode") that includes:
1. A Streamlined UI: Automatically hides all non-functional mobile features.
2. Native Surface Support: Built-in surface placement that works out-of-the-box for world-locked content.
3. Dedicated Documentation: A standalone API reference strictly for Spectacles-supported features.
At this stage, Spectacles development has evolved enough to deserve its own native environment and optimized workflow.