| name | spectacles-networking |
| description | Reference guide for the Lens Studio Fetch API and WebView component in Spectacles lenses — covering InternetModule (Lens Studio 5.9+), Fetch API via internetModule.fetch(Request) with bytes/text/json response handling, performHttpRequest, Internet Access capability, GET/POST requests, custom headers, Bearer auth, polling, timeouts, CORS/HTTPS, WebSocket and RemoteMediaModule for media from URLs, and bidirectional WebView messaging. Use this skill for any lens that calls a REST API, polls a JSON endpoint, loads remote images, embeds a webpage, or talks to a custom backend — including the Fetch sample. Use spectacles-ai for LLM/RSG calls, or spectacles-cloud for Supabase/Snap Cloud integration. |
Spectacles Networking — Reference Guide
Two main mechanisms for network access in Spectacles lenses:
- InternetModule — HTTP/HTTPS via the Fetch API (recommended) or performHttpRequest. From Lens Studio 5.9, these APIs live in
InternetModule; prior to 5.9 they were in RemoteServiceModule.
- Web View — embed a web page in the AR scene, with bidirectional JS messaging.
The Remote Service Gateway (RSG) is a third option but is specific to AI/cloud-model calls — see the spectacles-ai skill for that.
Official docs: Internet Access | Spectacles Home
Setup
- Enable Internet Access: Project Settings → Capabilities → ✅ Internet Access. Without this, all requests fail on-device.
- Fetch API: Spectacles OS v5.58.6621+ and Lens Studio v5.3+. Use InternetModule (Lens Studio 5.9+): add the module to your project and call
internetModule.fetch(request).
- HTTPS is required for publishable lenses; HTTP requires Experimental APIs and cannot be published. Never ship a lens using HTTP, even in preview builds shared with others — switch to HTTPS before distributing.
- Fetch only works in Preview when Device Type Override is set to Spectacles.
Fetch API (InternetModule)
Use InternetModule and construct a Request, then call internetModule.fetch(request). Response bodies use response.text(), response.json(), or response.bytes() (not body, blob, or arrayBuffer).
Basic GET
const internetModule = require('LensStudio:InternetModule')
this.createEvent('OnStartEvent').bind(async () => {
const request = new Request('https://api.example.com/data', { method: 'GET' })
const response = await internetModule.fetch(request)
if (response.status === 200) {
const data = await response.json()
print(JSON.stringify(data))
}
})
POST with JSON body
const request = new Request('https://api.example.com/submit', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ key: 'value' })
})
const response = await this.internetModule.fetch(request)
if (!response.ok) { print('HTTP error: ' + response.status); return }
const data = await response.json()
With authentication headers
const request = new Request('https://api.example.com/secure', {
headers: {
'Authorization': 'Bearer ' + myToken,
'Content-Type': 'application/json'
}
})
const response = await this.internetModule.fetch(request)
Async / Await Pattern
@component
export class FetchExample extends BaseScriptComponent {
private internetModule = require('LensStudio:InternetModule')
async onAwake() {
try {
const request = new Request('https://api.example.com/items')
const response = await this.internetModule.fetch(request)
if (!response.ok) {
print('HTTP error: ' + response.status)
return
}
const items: any[] = await response.json()
this.displayItems(items)
} catch (e) {
print('Network error: ' + e)
}
}
displayItems(items: any[]): void {
}
}
Handling Responses
On Spectacles, use bytes(), text(), and json() for response bodies (not body, blob, or arrayBuffer).
| Method | Returns | Use for |
|---|
response.json() | Promise<any> | JSON APIs |
response.text() | Promise<string> | Plain text or HTML |
response.bytes() | Supported | Binary data (images, audio) |
response.status | number | HTTP status code |
response.ok | boolean | true if status 200–299 |
response.headers.get('Content-Type') | string | null | Read a response header |
Always check response.ok before parsing:
if (!response.ok) {
print('HTTP error: ' + response.status)
return
}
performHttpRequest and Remote Media
For a simpler callback-based API, use internetModule.performHttpRequest(RemoteServiceHttpRequest.create(), callback). For downloading images, video, glTF, or audio from URLs, use internetModule.makeResourceFromUrl(url) and then RemoteMediaModule.loadResourceAsImageTexture() (or loadResourceAsVideoTexture, loadResourceAsGltfAsset, loadResourceAsAudioTrackAsset). See Internet Access for full examples. Use global.deviceInfoSystem.isInternetAvailable() and onInternetStatusChanged to react to connectivity changes.
Multipart Form Data (File Upload)
async function uploadFile(url: string, filename: string, blob: Blob): Promise<void> {
const formData = new FormData()
formData.append('file', blob, filename)
const response = await fetch(url, {
method: 'POST',
headers: { 'Authorization': 'Bearer ' + myToken },
body: formData
})
if (!response.ok) print('Upload failed: ' + response.status)
}
Web View
Web View renders a full web page into a texture that can be applied to any mesh in the scene.
Setup in Lens Studio
- Add a Web View component to a Scene Object.
- Set the URL in the component inspector, or set it at runtime via script.
- Apply the Web View texture to a Screen Image or a Mesh Visual material.
Scripting the Web View
webViewComponent.setUrl('https://myapp.example.com')
webViewComponent.evaluateJavaScript("document.getElementById('status').textContent = 'AR connected'")
webViewComponent.onMessageReceived.add((message: string) => {
const data = JSON.parse(message)
})
Sending messages from web page to lens
In the web page's JavaScript:
window.lensStudioMessage(JSON.stringify({ action: 'buttonClicked', id: 42 }))
Hardened Fetch Helper
Combines timeout, status check, and safe JSON parsing in one reusable function:
async function fetchJSON<T>(
internetModule: any,
url: string,
options: RequestInit = {},
timeoutMs = 10000
): Promise<T | null> {
const timeoutPromise = new Promise<never>((_, reject) =>
setTimeout(() => reject(new Error('Request timed out')), timeoutMs)
)
try {
const response = await Promise.race([
internetModule.fetch(new Request(url, options)),
timeoutPromise
]) as Response
if (!response.ok) {
print(`[Fetch] HTTP ${response.status} for ${url}`)
return null
}
return await response.json() as T
} catch (e) {
print('[Fetch] Error: ' + e)
return null
}
}
const data = await fetchJSON<{ items: any[] }>(this.internetModule, 'https://api.example.com/items')
if (data) displayItems(data.items)
Common Patterns
Poll for updates on a timer
let elapsed: number = 0
const POLL_INTERVAL = 5
const updateEvent = this.createEvent('UpdateEvent')
updateEvent.bind(() => {
elapsed += getDeltaTime()
if (elapsed >= POLL_INTERVAL) {
elapsed = 0
this.pollRemoteData()
}
})
Cache responses to avoid thrashing the network
let cachedData: any = null
let cacheTime: number = 0
const CACHE_TTL = 30
async function getWithCache(url: string): Promise<any> {
const now = getTime()
if (cachedData && (now - cacheTime) < CACHE_TTL) return cachedData
const r = await fetch(url)
if (!r.ok) throw new Error('HTTP ' + r.status)
cachedData = await r.json()
cacheTime = now
return cachedData
}
Request timeout with Promise.race
function fetchWithTimeout(url: string, timeoutMs: number): Promise<Response> {
const timeoutPromise = new Promise<never>((_, reject) =>
setTimeout(() => reject(new Error('Request timed out')), timeoutMs)
)
return Promise.race([fetch(url), timeoutPromise])
}
Permissions & Privacy
Combining internet connectivity with camera, microphone, or location in the same lens triggers Snap's Transparent Permission system: the OS shows the user a consent dialog on launch, and the device LED blinks while sensitive data is captured. Exception: calls via the Remote Service Gateway (RSG) do not count as external connectivity — you can use RSG with camera/microphone without triggering the Transparent Permission prompt.
Common Gotchas
- InternetModule (Lens Studio 5.9+): Use
require('LensStudio:InternetModule') and internetModule.fetch(request); global fetch may not be available. Enable Internet Access in Project Settings → Capabilities or network calls fail.
- Request constructor: Does not support taking another
Request as input; use a URL string.
- Response bodies: Use
response.bytes(), response.text(), response.json() — body, blob, arrayBuffer are not supported.
- Always check
response.ok before calling .json() or .text() — a non-200 response body may not be valid JSON and will throw.
- CORS: Web APIs must allow Spectacles' origin. HTTPS required for publishable lenses; HTTP requires Experimental APIs and cannot be published.
- Fetch does not time out automatically — wrap with
Promise.race if your backend might be slow.
- Web View performance: Large or animation-heavy web pages can hurt framerate. Prefer static or lightly interactive pages.
- Multipart uploads: do not set
Content-Type manually when using FormData — fetch sets it with the correct boundary.