Your connected lighting product is sourced in China, and its companion app is ready for an overseas marketing push. The brief asks for two additional App Store preview videos “to see which works.” Before commissioning them, decide whether you want to test an expression or direct different visitors to different feature stories.
Those are useful but distinct production assignments. One requires a comparison that can answer a question. The other requires an appropriate destination for each intended use.
Apple separates product-page testing from custom pages
Checked October 31, 2026, Apple’s Product Page Optimization overview describes randomly showing treatments to user groups to compare icons, screenshots and app previews. Product Page Optimization, or PPO, is not available for custom product pages.
Apple’s custom product page guidance describes different screenshots, previews and promotional text, unique shareable links, and keyword configuration for relevant search appearances. Pages need approval before becoming visible. These capabilities do not establish that a particular creative works better, or that a brand has a running experiment.
Two custom product pages with different videos do not automatically constitute Apple’s randomized default-page test. This is an evergreen procurement analysis using current documentation, not a new-feature announcement or an account test.
Write two different kinds of production brief
ONCE proposes choosing the assignment before quoting. If both are needed, scope them separately and identify shared recordings afterward. This is a production planning method, not an Apple procurement standard.
| Assignment | Question | Main deliverables | What it does not establish |
|---|---|---|---|
| Test default-page assets | Which expression performs better under the agreed conditions? | Baseline, defined candidate changes, version notes and deployment record | A universal winner across markets and products |
| Route visitors by use | Does each entry point lead to the relevant feature explanation? | Feature scripts, page-and-link mapping and route checks | That page conversion differences measure video quality alone |
A testing assignment needs a defined comparison
For a hypothetical lighting app, the question might be whether opening on room-group control or scheduling better explains the same app. Neither is a proven winner here. Confirm the testing route, eligible audience, metric and other page changes before recording.
If the desired inference concerns the video, keep track of changes to screenshots and icons too. Replacing the whole page can compare page packages, but it cannot assign the entire result to the preview. The production partner supplies the specified assets; the analysis owner decides what the evidence supports.
A routing assignment needs a coherent feature story
The same hypothetical brand might run one campaign about multi-room control and another about scheduled lighting. Their previews can explain different tasks rather than preserve a single-variable comparison at the expense of clarity. The entry promise, page content and actual app capability should agree.
A scheduling page may receive visitors already looking for that capability while another page receives broader traffic. A higher conversion rate does not, by itself, prove a stronger edit. Audience intent, source, country or timing may differ. Design a comparable validation separately if the decision is about creative effectiveness.
Conversely, one clear preview may serve multiple entry points. A platform’s page capacity is not a production target. Make another version when the user task warrants it, rather than for every campaign label.
Plan app recordings separately from live-action advertising
Apple’s App Previews guidance describes device-captured footage demonstrating app functionality and interfaces, with content kept inside the app rather than external shots of people operating a device. That applies to app previews; other App Store creative asset categories are distinct.
A lifestyle commercial for the connected hardware therefore does not automatically replace the app preview. Commission live action for the relevant off-store advertising use and actual app recordings for the preview. Coordinate the product facts and visual direction, but accept them as separate deliverables.
Have the product team confirm the build, language, account state and available features before capture. Demonstration rooms, connected units and schedules should support the intended task. Editing must not imply that an unavailable feature is already usable. Retain clean recordings and editable explanatory copy so a later interface change has a known update scope.
Connect files, pages and entry points in one usage map
Record each version’s purpose or test question, file ID, app build, language, destination page, actual entry point and owner. Test variants also need a change note; routed variants need the user task they explain. “English version two” is not enough to distinguish different assignments.
Before launch, check the agreed scope: asset and page approval, the actual destination reached from the entry point, and the correct language and feature content. Record the devices and environments inspected without turning a limited check into universal verification. Delivering a file and making it visible on the intended page are different stages.
Quote shared capture preparation, test edits, feature branches, localization, page coordination and route checking separately where applicable. Identify who manages account configuration and submissions. Production-only work should not silently include media operations or experiment analysis, and shared recording should not be charged twice.
Keep the purpose behind the version
For ONCE’s recurring content services, useful records connect actual feature recordings to their use, page and observed conditions. A successful routed page can motivate further work on that use; it does not automatically supply an editing formula for every market.
Start the next brief with one decision: are we comparing an expression, or helping different visitors understand their relevant task? Then purchase the versions and coordination that answer it. Explore more video marketing research when defining the broader campaign.
Sources and scope
Apple Developer / App Store Connect Help, “Overview of product page optimization” and “Configure multiple product page versions”; Apple Developer, “App Previews.” All checked October 31, 2026. Apply each requirement to its documented asset and page type.
The briefs, usage map and lighting scenario are ONCE analysis or hypothetical planning. No client experiment, conversion rate, download gain or achieved margin improvement is claimed. The original AI cover is a physical branching concept.
