A digital-platform launch depends on screens and live demonstrations, so photographs must show the right screen at the right moment without exposing private data. Ask the product team which screens are cleared, which accounts and data are test data, and when the presenter moves between views. We plan positions and release checks around that.
Software and online services are hard to photograph because the product lives on a screen. A good launch picture shows the screen, the presenter and the audience together, without giving away more than intended.
This guide belongs to our overview of launch and press-event photography. For device-centred launches with trial areas, see consumer-device launches with hands-on trial areas.
Why screens need a plan
Screens are bright, move and change. Photographed badly, they appear washed out, striped or too dark. Photographed well, they show the product exactly as the audience sees it.
Our guide to stage lighting, LED screens and mixed light explains why a screen behaves differently in photographs and what that means for exposure and timing. Production teams can help by telling us the screen sizes and refresh settings they are using.
Identify the screens that matter
A launch usually has several screens: a main stage screen, side screens, a presenter's laptop or a handheld device. Each shows something different.
Ask the product team to name the screens that carry the story. Perhaps the main screen shows the new dashboard while a side screen shows a customer example. Mark these so the crew knows where to point the camera at each stage.
Decide what may be legible
Some screen content is meant to be read in photographs, such as a headline feature or a pricing description approved for release. Other content must stay unreadable: internal metrics, customer names, unreleased features or test accounts.
Create a simple list of cleared views and not-cleared views. The authorised-subjects approach in launch events involving unreleased products applies here too. Our guide to photography around projected slides and confidential screens covers practical measures.
Protect private and test data
Live demonstrations often use real-looking data. A name, an email address or a transaction can appear in the corner of a screen and end up in a press photograph.
Ask the team to use clearly fictional test data and to check the demo environment before doors open. Our guide to event photographs that show confidential business information explains how such details slip into frames. If a customer appears on screen, check their consent before any release.
Follow the presenter's moves
A digital demonstration has natural steps: logging in, opening a view, showing a result and closing. The photograph that works best usually combines the presenter and the screen in one frame.
Ask the presenter or product lead for the sequence and the cue for each change. Our guide to photography cues from the emcee and floor manager describes how cues are shared. The presenter keeps their own pace.
Captions and technical accuracy
A caption on a launch photograph may describe what the system does. Such wording should come from your product team, not from our photographer. Technical claims stay with your team.
Our event photograph caption worksheet helps collect the names, titles and product terms to use. If you plan to publish captions that describe performance or capability, check the wording against your own technical documentation.
A hypothetical example
Imagine a software company launching an analytics service in a hotel ballroom. The presenter demonstrates three views on a main screen while a customer panel sits on stage. The product team marks the first two views as cleared and the third, which shows a client's dashboard, as not cleared.
We would plan a position that shows the presenter and the main screen together for the first two views, then reposition for the panel during the third. Images are checked against the list before release. This illustrates how screen planning works.
Before the demo day
Send us the order of views your presenter will show, which screens are cleared to be readable and who checks images for private data. Add your approved caption wording, and we will confirm the plan in writing.
Checklist
- List the screens: stage, side, handheld and presenter devices.
- Mark which screens and views are cleared for legible capture.
- Confirm that demo data is test data.
- Share the demonstration flow and the key view changes.
- Agree who checks images for private information.
- Supply approved wording for captions.
Send us the demonstration flow, the screens in the room, the data being shown and who clears images, and we will propose coverage and confirm it in writing.
Ask about your platform launchCommon questions
Can the screen content be photographed legibly?
Only if your team allows it. Some content is meant to be readable in photographs, such as a headline feature. Other content must stay unreadable. Tell us which is which, and we frame or mark images accordingly.
How do we avoid capturing private data on a demo account?
Ask your team to use clearly test data and to confirm it before the event. From the audience position, we cannot always tell what is private. Where there is doubt, we hold the image for review before release.
What if the demonstration fails or the screen changes?
Live software can stall. Our crew keeps recording the room and the presenter as the session continues. Our separate guide on demonstrations that do not go to plan explains how to handle it.
Can you confirm technical details in captions?
Captions should come from your product team. Send us accurate wording, names and product terms, and we use them as supplied.
Ask about your platform launch
Send us the demonstration flow, the screens in the room, the data being shown and who clears images, and we will propose coverage and confirm it in writing.
What happens next: You send your event details on WhatsApp. Our team reads the brief, asks what is missing, then confirms in writing whether the date, venue and coverage can be booked, with a quotation. Opening WhatsApp does not send anything, and a message is not a booking until both sides confirm.
Last reviewed: