What does projection-first mean for a production?

Projection-first means the shared display is the primary audience route because representative seats have verified readability, the language plan fits the shared frame, and nobody must configure a personal device to receive the advertised service. It does not rule out a supported alternative.

When should a production start with mobile subtitles?

Mobile-first is a reasonable starting point when personal language choice, privacy, or reading position is central, projection cannot serve intended seats evenly, and the venue can support entry, discreet help, a non-phone alternative, and show-time recovery.

Can the correct decision be that neither delivery path is ready?

Yes. If the team cannot yet provide readable placement, a usable audience-entry path, adequate support, or a credible fallback, not-yet-ready is an honest planning result. Narrow or pilot the promise before advertising it broadly.

How should a theatre pilot mobile and projected subtitles?

Use one representative performance, test projection from intended seating areas, and test mobile entry from public instructions. Explain how feedback will be used, obtain informed consent, fairly compensate requested expertise, rehearse likely failures, and record front-of-house and operator load before choosing a rollout model.

Mobile or Projected Surtitles? Choose the Reading Route People Can Rely On | SurtitleLive Planning

Short answer

Choose projection, personal-device subtitles, both, or neither by the reading route people can genuinely rely on—not by which screen seems newer. A shared display can be the most welcoming route; a personal device can protect language choice or privacy. Neither should require an audience member to disclose a need, bring a particular phone, or absorb a failure the production has not prepared for.

Delivery Is a Choice About Reading, Privacy, and Support

Two venues can use the same subtitle technology and produce very different audience experiences. A clear projection in a steep, purpose-built auditorium may be easier to read than repeatedly lowering one’s gaze from the stage to a phone. The same projection in a flat black box, a balcony with masking, or a touring venue with no stable screen position may serve the room unevenly.

Personal-device delivery can change the equation when audiences need different languages, a nearer reading position, or a more private route. It also creates an entry journey. The production must account for device choice, battery, connectivity, venue phone policy, understandable browser steps, discreet front-of-house help, a non-phone alternative, and the shift of attention between screen and stage.

This guide turns those tradeoffs into a practical decision matrix. For the underlying accessibility and audience-agency principles, first read Projection vs. Mobile Surtitles: Which Fits Your Audience and Venue?.

Four Honest Outcomes—None Is a Status Hierarchy

Projection-first: a shared display serves intended seats and the language plan without making people configure a device.
Mobile-first: personal reading position, language choice, or privacy is central, and the venue can support the whole entry journey.
Hybrid: each route removes a different, verified barrier, and the team can operate and recover both without splitting attention unsafely.
Not ready: a proposed route cannot yet meet a critical reading, entry, staffing, or recovery condition. That is a responsible result, not a failure to appear innovative.

Production Scenario Matrix

Production condition	Likely starting point	What could change the answer
Fixed proscenium room, verified sightlines, one shared translation	Projection-first	Side seats, balconies, or audience members who need another reading position are not served comfortably.
Festival or tour with changing rooms and screen positions	Mobile-first or hybrid	Audience connectivity, phone policy, and front-of-house capacity are weak.
Several audience languages needed at the same performance	Mobile-first or hybrid	Most people share one language and the additional tracks can be served another way.
Phone-restricted production or audiences facing significant device barriers	Projection-first	The venue can supply, explain, and support dedicated devices without stigma.
Mixed needs: shared translation plus a personal accessibility track or language choice	Hybrid	The crew cannot rehearse and recover two delivery paths reliably.

Audit the Route Without Making People Prove a Need

Map which intended seats can read the projection comfortably—not merely see that a screen exists.
List the language and access tracks that must coexist, and whether they can share one visual frame without shrinking readability.
Ask a new user to enter the mobile viewer from the public instructions, with no saved link, backstage explanation, or staff shortcut.
Estimate how many people may need help or a non-phone route, and whether front-of-house can assist discreetly without demanding public disclosure of need.
Rehearse the first credible failure for each path: blocked projection, lost signal, connection trouble, a device that cannot join, or cue recovery after a performance deviation.

Let the Unserved Route Decide

Do not average away a serious barrier. Excellent mobile language choice does not compensate for an entry process that many intended users cannot complete. A beautifully integrated projection does not compensate for seats from which the text is unreadable. If one audience group the production has promised to serve cannot reach the service, revise the configuration or narrow the promise.

Hybrid delivery should clear the same test twice. It is justified when two paths remove different barriers, not when “more channels” is treated as evidence of inclusion. If staffing or recovery becomes fragile, a well-run single path plus a clearly communicated alternative may be more responsible than two unreliable paths. Do not call either route universally accessible before testing the conditions that make it usable.

Pilot the Promise Before Publishing It

Choose one representative performance, publish the same instructions the audience will receive, and test from real seats. Where possible, invite people who use the intended access paths, explain how their feedback will be used, obtain informed consent, and provide fair compensation for requested time and expertise. Participation should never require someone to disclose a disability or language need publicly. Record where reading, entry, attention, staffing, or recovery fails, and define which result leads to revision, a narrower promise, or no rollout. The purpose of a pilot is not to prove the preferred screen was right; it is to expose which promise the team can keep.

SurtitleLive can support a prepared cue set feeding projection and browser-based audience delivery. It does not choose the format for a venue, provide translators, caption writers, access specialists, connectivity, devices, or a live operator, or certify accessibility or legal compliance. Seat testing, audience guidance, a supported non-phone alternative, and rehearsed recovery remain production responsibilities. Enable only the routes the team can explain and operate reliably.

If the next question is how to introduce mobile access without committing the whole season, continue with Pilot or Full Rollout?, then compare QR Code Subtitles for Audiences and Subtitle Backup and Fallback for Live Performance.