Docs
How to build screen-accurate device props with Glass Double — from your first scene in the Designer to presenting it on set. Everything on screen is a fictional OS with no real-brand UI to clear.
1Getting started
You build every prop in the browser-based Designer, then present it on set or hand off an export. The core loop is five steps:
- Open the Designer. Head to /designer. It works fully offline — your props stay on the device until you choose to sign in and sync.
- Pick a fictional OS skin. Choose a device look (Lumen, Aria, Terra, and more) and an appearance — light or dark. Skins are data, so you can re-theme the whole device later without rebuilding the scene.
- Choose a prop module. Add one of the thirteen screen types — a call, a message thread, a notification stack, a home screen, and so on — and edit its content: contact names, message text, timings, wallpapers, and status bar.
- Save to the cloud. Sign in to save your props and uploaded media so what you built at the office is ready on set. Cloud sync and unlimited saved props are part of the paid plans; you can design everything for free first.
- Present on set or share the link. Hit Present to open the scene full-screen at /prop, or copy that link to open the same prop on the phone that’s actually in frame — any device with a browser.
New to the product? The features overview is a good tour of the whole kit before you dive in.
2Prop modules
A prop is built from one of thirteen screen modules — each a self-contained, fictional stand-in for the kind of app a scene calls for. Pick the module that matches the shot, then style it with any skin.
Call screens
Fake incoming and active voice or video calls with custom contact names, fictional numbers, avatars, and lock/awake states. Ringtones are synthesized at runtime, so nothing on screen (or in the audio) is a real brand asset.
Messages
Scripted SMS/chat threads — text bubbles, voice notes, and file chips — that reveal on cue so an actor can deliver a line as each message lands, timed for the take.
Notifications
Stackable lock-screen and banner notifications you sequence frame by frame, so the story beats you need arrive exactly when the camera is rolling.
Home screens
Fictional home layouts with app grids, folders, a dock, widgets, and wallpapers — fully themeable through the active skin, with no real OS iconography.
Green screen
Chroma fills with built-in registration markers so VFX can track the screen and replace it in post — the safest possible clearance path when the content is added later.
Playback
Locked-screen media playback and now-playing states for scenes shot around a paused or idle device, without exposing any real streaming or music brand.
Feed
A generic social feed of posts and reactions — the doom-scroll on camera without any real-platform logo, wordmark, or UI to clear.
Maps
A fictional wayfinder with routes, pins, and turn-by-turn cards for navigation and location beats, standing in for a real mapping app.
Wallet
Transactions, balances, and passes — statements and payment moments that read on camera as a believable finance app while staying entirely fictional.
DMs
A direct-message inbox with a conversation list, unread badges, and threaded replies for messaging-app scenes that need more than a single thread.
Stream
A streaming-service home — content rows, hero artwork, and titles — for the TV-in-hand watch scene, with original art in place of any real service.
An inbox and message view for the classic on-screen email reveal — cleared and fictional, so the message that drives the plot is safe to show.
Car dashboard
A landscape car cluster / infotainment display — speed, gear, range, a nav card, now-playing media, and climate — rendered in its own dashboard frame rather than a phone. For scenes shot in a vehicle and any non-phone glass on set.
3Skins & clearance
A skin is the entire device look — status bar, app chrome, typography, colors, and iconography. Because skins are data, swapping one re-themes your whole prop across fictional operating systems with no rebuild and no real-brand exposure. The bundled skins span modern and period-accurate eras:
Lumen
The flagship modern phone look and the default skin — clean, contemporary, brand-neutral.
Aria
A rounded, glossier modern era for a warmer, more consumer feel.
Terra
An alternate contemporary system for productions that want a distinct device identity.
Gloss
An earlier, skeuomorphic era — period-accurate for scenes set a few phone-generations back.
Verge
A bold, high-contrast system for a sharper, more editorial device.
Halcyon
A soft, muted palette for a calmer, understated handset.
Onyx
A luxe monochrome OLED look — true black, hairline dividers, a single gold accent. For an executive, a thriller lead, or a premium brand universe.
Bloom
A bright, friendly consumer look — warm cream, big rounded corners, a soft coral accent, playful icons. For a teenager, an influencer, or a rom-com lead.
Why fictional UI reduces clearance risk. Real iOS and Android interfaces, app icons, logos, and wordmarks are protected by trademark and trade dress. Showing them without a licensing deal creates errors-and-omissions (E&O) exposure and can block delivery. Glass Double leads with original, cleared fictional UI — so there is nothing on screen that needs a real-brand clearance in the first place.
Each scene also carries a presentation clearance intent: a neutral, flattest rendering (the brand-safe default) or a slightly glossier, more native-feeling look. Both stay fictional — the intent only nudges the chrome, never the brand safety.
The E&O clearance log. Glass Double records which fictional skins and assets each shot used, and can produce a per-shot clearance / errors-and-omissions log to support your production’s delivery paperwork. These logs are informational only — they are not legal advice and not a guarantee that a shot is cleared. Final clearance always rests with you and your counsel; see the Terms for the full clearance point.
4Collaboration & cloud sync
Signing in unlocks the cloud: your props and uploaded media sync across your devices, and you can work with your crew from one source of truth. Authentication is handled by Convex Auth — we store a hashed password, never plaintext.
- Projects. Group related props into a project so a whole unit — prop master, playback op, director — works from the same set of scenes.
- Inviting collaborators. Share a project by email and assign a role. A viewer can open and read the shared props; an editor can additionally save changes. You can invite anyone by email — if they don’t have an account yet, the invite is applied automatically the first time they sign in. Only the owner can invite or remove collaborators, change roles, or delete the project. Shared projects show up in each collaborator’s “Shared with me” list.
- Public share links. From your projects dashboard, create a read-only link for any prop. Anyone with the link can view the prop at /p/<token> — no account needed — which is handy for sending a director or client a quick look. The link stays private to whoever you send it to (it isn’t indexed), and you can revoke it at any time.
- Team plan. On the Team plan, the owner holds a per-seat subscription and every member gets Crew-level access. Invite teammates by email from your account page — again, they can join before they even have an account.
- Version history. Every save snapshots the prop, so you can review prior versions newest-first and restore any of them — handy when a change on set needs to be rolled back between takes.
- Cloud sync. What you build at the office is ready on set. Uploaded media is stored securely and travels with the prop.
5On-set & operator
The same scene renders in three surfaces, all decoded from the one shareable /prop link:
- Present. A full-screen preview with light Designer/Fullscreen chrome — the self-operated view for checking a scene or presenting it yourself.
- On-Set. A clean, chrome-free surface (/prop?…&onset=1) for the phone that’s actually in frame. It shows nothing but the prop and quietly listens for remote cues.
- Operator. A separate console (/operator) that runs on a different device or browser and cues the on-set surface without anyone touching the hero phone. Buttons ring an incoming call, reveal the next scripted message, fire the next notification, or reset the prop to its authored start.
The on-set surface and operator console pair on a shared join code (session), so several props can run on set at once without crossing cues. The Designer ships all three links pre-paired for you.
Cue sheets. The operator console can also run a pre-planned cue sheet — an ordered list of labelled cues you build ahead of the take (e.g. “phone rings as Mara enters” → “text lands” → “alert”). During the take you step through it hands-free with one GO button (plus Back and a reset to the top), so the operator watches the monitor instead of hunting for the right button. Cue sheets are saved per join code on the operator’s device.
Remote cueing & hardware triggers. On the native apps, a hardware trigger can fire a cue hands-free — for example an Android hardware button. (On iOS a physical volume-button trigger needs a small custom native plugin and no-ops until then.) The prop surface can keep the screen awake and hide the system status bar so the device reads purely as the character’s phone.
6Exports
When a shot needs a file rather than a live device, export the current scene straight from the Designer:
- PNG (transparent). A high-resolution still of the live preview on a transparent (alpha) background — the static-mockup deliverable, ready to composite over footage.
- Video. Record the preview playing back to a downloadable WebM — the scripted sequence captured as it animates.
- Transparent (alpha) video. The same recording on a see-through background so a compositor can lay the device over your plate. Requires a browser with alpha-codec support; it degrades gracefully where that isn’t available.
- Contact sheet. One labelled PNG that composites the prop in each appearance (light and dark) side by side — a quick reference for continuity.
- Clearance-log PDF. A printable one-page clearance / E&O report for the current scene, produced via your browser’s print-to-PDF, to file with your delivery paperwork.
7Accounts & billing
Every prop screen and fictional skin is free to design. You pay only for cloud continuity across devices and for production-grade features. Plans:
- Free — $0 forever. All prop types, every fictional skin, three saved props in the cloud, single device.
- Crew — $59/year (also $9/month or $149 lifetime). Everything in Free plus unlimited saved props and projects, cloud continuity across your devices, and custom imports.
- Production Pass — $49 per 30-day project. Everything in Crew for the length of a shoot, shared across up to 6 devices on one project. Web-only, no subscription.
- Team — $29 per seat / month. Everything in Crew for every seat, shared projects with editor/viewer roles, the E&O clearance trail, and an approvals / sign-off workflow. Invite anyone by email — they join when they sign in.
- Studio / Enterprise — custom. For rental houses and studios: everything in Team plus SSO on request, a DPA, rental packages, volume seat pricing, and priority onboarding. Arranged directly with us.
Compare everything on the pricing page. Payments run through Stripe — we never store your full card details. Manage your subscription, open the Stripe billing portal, or check your current plan any time on your account page.
8FAQ
Is it really clearance-safe?
Glass Double gives you original, fictional UI so you never need to show real, protected OS or app branding — which is what creates E&O exposure. That removes the riskiest part of an on-screen device. But you are still responsible for the content you add (contact names, logos, images) and for your production’s final clearance. The clearance log is informational, not legal advice — always confirm with counsel before delivery.
Does it work offline?
Yes. The Designer runs fully in the browser and works offline — your props stay on the device. It also keeps a local draft of your work, so if the tab reloads or the browser crashes in a set dead zone your in-progress scene is restored when you come back. If you’re signed in, a save made offline is queued and syncs automatically the moment you reconnect — the Designer shows an honest “offline — will sync” status so nothing looks lost. Cloud sync, saving across devices, and collaboration require signing in and an internet connection.
Web, iOS, or Android?
One shared engine renders on web, Android, and iOS — the prop can be the phone in frame or a browser on a tablet. Hardware-trigger cueing is a native-app capability (see On-set & operator).
Can I cue a scene without touching the hero phone?
Yes — that’s the Operator console. Run it on a second device, pair it to the on-set surface with the shared join code, and ring calls, reveal messages, or fire notifications remotely.
Can I hand off a file instead of a live device?
Yes. Export a transparent PNG, a video, a transparent (alpha) video, a light/dark contact sheet, or a clearance-log PDF straight from the Designer. See Exports.
Do I have to pay to try it?
No. Designing props and using every skin is free. Paid plans add cloud continuity, unlimited saved props, and production features like the E&O clearance log. Compare on the pricing page.
Build your first prop screen.
Open the Designer and start free, or compare plans for cloud sync and clearance logs.