At a glance
| Field | Detail |
|---|---|
| What | Choose a capture and editing approach for app demonstration videos. |
| Who it matters to | App advertisers preparing creator footage for Meta campaigns. |
| Where | Pixel screen capture; Facebook and Instagram as intended advertising destinations. |
| When it applies | When an app demonstration needs a presenter visible alongside the interface. |
| Action | Review device support, capture scope, layout, and the reporting plan before commissioning footage. |
Android Screen Reactions combines a screen recording with a live selfie video. For app advertisers preparing Meta creative, the useful decision is whether to capture the demonstration and presenter together or prepare the footage separately. Our suggested approach starts with what must remain visible, then checks how the finished asset will be evaluated.

Choose the capture mode before writing the brief
Google's Screen Reactions overview describes simultaneous capture while someone navigates an app, with a movable and resizable selfie overlay. It names Pixel 6 and newer phones and requires Android 17. Support across other Android manufacturers is not specified in the cited documentation. Check the creator's actual device before making this capture method part of the brief.
The same overview says Screen Reactions requires recording the entire screen rather than a single app. Our interpretation: review the full demonstration route before recording, including any transitions away from the promoted app. Ask the creator to inspect the saved footage for unintended material before submitting it for advertising review.
Google's Pixel recording instructions separately document single-app recording, audio controls, and simultaneous screen and selfie capture. They also state that front-camera zoom is unsupported. For a demo in which a small interface detail carries the message, check whether moving or resizing the presenter leaves that detail readable.
Compare the production routes
The options below combine Google's capture documentation with Meta's description of Edits. The suggested checks are our interpretation of those capabilities.
| Approach | Source-backed capability | Control or limitation | Suggested check |
|---|---|---|---|
| Capture a live reaction | Screen Reactions records the presenter and screen together. | Requires entire-screen capture; the selfie overlay can be repositioned. | Rehearse the app action and presenter position together. |
| Record the app separately | Pixel offers a single-app recording option. | This is distinct from the entire-screen requirement described for Screen Reactions. | Consider this route when the brief calls for isolated interface footage. |
| Edit the demonstration | Edits provides a frame-accurate timeline, clip-level editing, and green-screen effects. | Placement-specific ad eligibility: Not specified in the cited documentation. | Review whether separate clips would make narration or pacing revisions easier. |
| Export a review copy | Edits supports exports without added watermarks. | Export guidance supplies no placement-specific ad specifications. | Keep the approved file identifiable in the campaign review. |
Review the finished asset and its reporting separately
Meta describes Edits as supporting direct sharing to Facebook and Instagram as well as exporting elsewhere. Its announcement also describes feedback on factors affecting distribution, including skip rate. Those are useful capabilities to consider when choosing an editing tool; the announcement does not establish that Screen Reactions footage improves app advertising performance. Meta's Edits announcement
For production review, we suggest watching the finished demonstration at the size a viewer will encounter it. Check that the presenter does not cover the action being explained and that narration matches the visible app behavior. If the viewer needs to read an interface label to understand the benefit, make readability an explicit acceptance criterion. These are suggested creative checks, rather than platform requirements established by the sources.
For performance review, AppsFlyer's Creative Optimization Overview documentation describes grouping by creative, ad ID, app, geography, platform, orientation, and resolution. It includes in-app event metrics and identifies partner metrics separately from AppsFlyer metrics. It also warns that performance data can appear without a creative preview when the asset was not retrieved from the network.
Our suggested implication is to verify the link between the approved video and its reporting row before interpreting results. Keep the capture device in production notes; review the audience platform using the reporting dimension. A phone used to make a video does not, by itself, establish which audience produced the reported outcome. Connect these checks to the creative review loop.
What to review
- Check the creator's device and operating system against the documented capture scope.
- Review the entire-screen recording for unintended content and obscured interface details.
- Compare live capture with separate recording when revisions are likely.
- Check the exported asset against the approved demonstration and narration.
- Verify the creative or ad ID, preview availability, audience platform, and metric source before evaluating performance.



