The short answer
Most Spectacles builds fall into one of three tiers. The table below maps complexity to timeline. All figures run from confirmed brief to event-ready build.
| Complexity tier | What it includes | Typical timeline |
|---|---|---|
| Simple (single interaction) | One hand gesture, static world AR, no multi-user | 4 to 6 weeks |
| Standard (brand activation) | Multiple interactions, product reveal, hand tracking, 1 to 3 devices | 6 to 9 weeks |
| Complex (spatial installation) | Multi-user, world mesh, spatial anchors, custom AI layer, 4+ devices | 10 to 14 weeks |
Add 1 to 2 weeks for event prep and on-site testing if the activation is in a new physical space that the Lens has not been tested in.
Phase 1: concept and scoping (1 to 2 weeks)
What happens: the studio reviews the brief, identifies what is technically feasible on the Spectacles hardware, and produces a concept document with interaction flow, hardware count, and a production scope. If the brief arrives without key information (event date, space dimensions, number of simultaneous users), this phase extends until those answers are in.
What clients can do to keep this moving: answer questions in the same business day. The scoping phase stalls most often because the client or agency has not locked the event date, the physical space, or the hardware count. These are not details that can wait until later. They determine the entire build architecture.
Phase 2: Lens build (3 to 5 weeks)
What happens: the Lens is built in Lens Studio 5.0 using the Spectacles SDK. The developer works through interaction logic, 3D asset integration, hand tracking calibration, and performance optimisation. Iteration happens on hardware throughout.
Core interaction prototype. The hand tracking logic and primary AR moment are functional on device. Not visually polished, but the mechanic works.
Asset integration and visual build. 3D models, textures, animations, and audio come in. The experience starts to look like the finished product.
Performance pass and edge case testing. Frame rate is checked on all target devices. Failure states (user walks out of range, tracking is lost, device is idle) are handled. The build is tested for 60-minute continuous sessions.
What clients can do to keep this moving: consolidate feedback. If the agency team gives notes and the brand team gives separate contradictory notes two days later, the build loses a week. One consolidated set of notes per review round.
Phase 3: agency review and revisions (1 to 2 weeks)
What happens: the agency (and optionally the brand team) puts on the Spectacles and reviews the build. Feedback comes back as a consolidated list. The studio addresses revisions. A second review pass confirms sign-off.
This phase requires hardware access on the agency side, either via the studio shipping a device for review or a visit to the studio. Video recordings of the Lens running on Spectacles are useful context but are not a substitute for putting on the glasses. Spatial experiences behave differently when experienced on the hardware versus watched on a screen.
What stalls this phase: feedback sent without hardware access, creative direction changes that require rearchitecting the interaction logic (these belong in Phase 2, not Phase 3), and waiting for brand team sign-off that is on a different approval timeline than the campaign build.
Phase 4: hardware testing in the live environment (1 week, if possible)
What happens: the Lens is tested in the actual physical space where the activation will run. Lighting conditions, ceiling height, ambient light levels, and crowd density all affect AR performance. A Lens that performs perfectly in a studio can behave differently in a dimly lit event venue or a brightly lit retail space.
This phase is optional for standard indoor activations where the environment is predictable. It is strongly advisable for outdoor activations, unusual lighting environments, or large-scale spatial installations where world mesh accuracy depends on the specific space.
Phase 5: event prep and on-site (1 week buffer + event day)
What happens: device setup and pairing, final hardware check, briefing of event staff on device handling and reset procedures. On event day: pre-event hardware test in the live space, activation running, on-site support for troubleshooting.
What to plan for: bring spare devices if the activation is longer than 4 hours or involves more than 3 simultaneous users. Spectacles batteries last approximately 4 hours of mixed use. Have a charging rotation plan.
On-site support is separate from the build scope. Confirm with the specialist studio how many days of on-site support are included and what happens if the event extends or a second day of activation is added.
Where projects lose time
- Late brief information: the event date, the physical space, and the hardware count are needed in Phase 1. Every week they are missing is a week the build cannot start with full information.
- Feedback consolidation: two rounds of feedback from two separate stakeholders who have not aligned is worse than one round from one person. One point of contact, one consolidated list per review round.
- Scope change in Phase 3: adding a new interaction or a second AR mode in the review phase requires going back to Phase 2. This adds 1 to 2 weeks minimum and usually runs into the event date.
Rush builds: what is achievable and at what cost
A 4-week build is achievable for a simple single-interaction Lens if the brief is complete and confirmed at week zero, no significant revisions are made after week 2, and the studio can prioritise it above other work (which typically involves a rush rate on top of the standard build fee).
A 3-week build is possible for very focused builds with a client who can review and approve within 48 hours at each stage. It is not recommended for a first-time smart glasses activation where the agency or brand team has not worked with the hardware before.
Rush builds carry a higher risk of undiscovered edge cases making it to the event. The performance testing and edge case handling in Phase 2 is where most Lens stability issues are caught. Compressing this phase compresses the error margin.
Insights newsletter
Smart glasses, AR campaigns, spatial computing.
Straight to your inbox. No noise.
SubscribeFrequently asked questions
How long does it take to build a Snap Spectacles lens?
A standard brand activation Lens takes 6 to 9 weeks from confirmed brief to event-ready build. A simple single-interaction Lens can be done in 4 to 6 weeks with a complete brief and fast feedback cycles. A complex multi-user spatial installation takes 10 to 14 weeks. These figures assume a confirmed brief at week zero, one review round per phase, and no significant scope changes after Phase 2.
What is the minimum lead time for a smart glasses activation?
The practical minimum is 4 weeks for a focused simple Lens with a client who can review and approve quickly. For a standard brand activation, 8 weeks from brief to event is a safer target. Brief your smart glasses studio before you brief the event production company. The glasses build is usually the longest lead-time item in the activation, and it is the one most commonly briefed last.
Can a Snap Spectacles experience be built in 2 weeks?
Not to a quality that is reliable at a public brand event. A 2-week build leaves no time for hardware performance testing, edge case handling, or meaningful agency review. A Lens with untested edge cases at a public activation means staff resetting devices in front of guests. Brief earlier or scope down to what can be built and tested properly in the time available.
What can slow down a smart glasses build that is not the studio's fault?
Three things delay builds on the client side: late confirmation of the event date or physical space (both affect the build architecture), split feedback from multiple stakeholders who have not aligned (each contradictory round adds a week), and scope additions in the review phase. A studio that is given a confirmed brief, a single point of contact, and consolidated feedback per round will deliver on time. Most slippage comes from the brief, not the build.
Planning a smart glasses activation?
Share your event date and brief. We will tell you what is achievable in the time you have.
Replies within 48 hours, straight from the studio.
Start a project