App Preview Video Production for iOS and Google Play

The App Store preview autoplays with the sound off in search results, so the poster frame and the first three seconds decide almost everything, and a logo animation at the front is how most previews lose. We cut iOS previews at 17 to 22 seconds inside Apple's 15 to 30 second window, opening on the app doing the single thing your strongest keyword implies. The Play video is a separate edit rather than the same file: it is YouTube-hosted, plays on tap with sound, and sits above the screenshots, so it has a longer runway and needs an audio track that carries meaning instead of mood. How the footage is made: Captured on device. Apple requires app preview footage to come from the real app, and previews built mostly from live action or motion graphics get rejected. We have had them rejected. So the pipeline is a build, a capture session on current hardware, and compositing only where Apple allows it: hands and gestures, contextual framing, transitions. Where a screen cannot be shown, we cut around it rather than mock it, which matters in banking, where the interesting screens contain real balances and the compliant screens contain sample data. What is delivered: ProRes 422 HQ masters, store-encoded H.264 at 1080 by 1920 and 886 by 1920, poster frames chosen deliberately rather than left on frame one, a landscape thumbnail and an unlisted YouTube upload configured without end screens or suggested videos for Play, and the editing project with the raw device captures. You own the source. Two years from now, when one screen has been redesigned, you should not have to come back to us for a re-cut. Localisation without voiceover: We do not put voiceover on a preview that autoplays muted. Burned-in text does the work, held long enough to read at about fifteen characters per second. German runs 25 to 30 percent longer than the same English sentence, so a German cut cannot be the English timeline with new words dropped in. It is re-timed, and where it will not fit we shorten the claim rather than speed up the reading. That is why German and English are quoted as two edits and not as a translation line. Order of operations: We will not produce video for a listing whose screenshots have not been tested. The preview is built on the same claim hierarchy as the gallery, and if that hierarchy is unproven we are producing an expensive asset on a guess. If your screenshots are untested, do that first, with us or with anyone competent, and come back. Measurement: The video ships as a Product Page Optimization treatment against a no-video baseline wherever your traffic supports the test. Video does not always win. On some utility and finance apps the preview lowers conversion by pushing the screenshots further down the page. We would rather find that on your app than repeat the industry line that every app needs one. Not included: Brand film, actors, stock footage, licensed music beyond a standard library track, and paid social ad creative. Ad creative shares nothing with a store preview except the source footage: different hook, different length, different measurement loop. We do not pretend one file serves both, and we hand the raw captures to whoever makes your ads. Not for you if: You are pre-launch and want the video for the launch deck, because you will re-cut it within a quarter as the product moves. Not for you if the approval chain includes people who have never watched a muted autoplay in a search result, because every note will be about the logo.