Record one complete flow
Capture a single job from start to finish on the device your users actually use. A thirty-second flow that ends in a visible result beats a long tour of every screen.
Record the one flow that makes your app worth opening, then turn it into demo videos that show each step clearly, with captions for silent autoplay, voice-over for context, and a portrait cut for phones.
Built for mobile and web app teams that need to show the core flow to new users, reviewers, and launch audiences without booking a production.
Best moments
Workflow
Capture a single job from start to finish on the device your users actually use. A thirty-second flow that ends in a visible result beats a long tour of every screen.
Break the recording into steps a viewer can follow without touching the app: what they start with, what they tap, and what they get back.
Use portrait for phone-first surfaces like social feeds and onboarding, and landscape for landing pages, docs, and anywhere the viewer needs to read the interface.
Example angle plan
Use these as starting points, then edit the script, claim strength, and CTA to fit your real launch.
Open on the output the app produces, then rewind to the taps that created it.
Walk a new user through the first session so they reach value without guessing.
Show a single capability end to end instead of a tour of every tab.
Show the old way (the spreadsheet, the notes app, the manual steps), then the app flow.
Count the taps or seconds from open to done, and make that number the hook.
Frame the same flow around one person and one moment in their day.
An app demo video has one job: get a stranger from "what is this?" to "I can see myself using it" before they scroll away. The viewer should see a real screen within the first few seconds, follow one flow without pausing, and understand what they get at the end. Most weak app demos fail by trying to show everything, every tab and every setting, so nothing sticks.
The flows that demo best are short and end in something visible: a generated result, a booked slot, a finished edit, a synced list. If your app only proves its value after a week of use, demo the moment a user first sees that value and say how long it took to get there, rather than compressing the whole journey into a montage.
A demo video answers "how does it work?" by showing the flow. A promo video answers "why should I care?" with a hook, one benefit, and a reason to download now, and it may show the interface for only a few seconds. Most apps need both: the demo for the landing page, onboarding, and help center, and several promo cuts for social and launch day. Both can come from the same recording by changing the angle rather than the footage.
On iPhone and Android, use the built-in screen recorder and turn on Do Not Disturb or a Focus mode so notifications never land in the shot. Use realistic sample data rather than an empty account, because an empty state does not demo anything. For web apps, record at normal browser zoom, hide bookmarks and extensions, and keep the cursor still between actions so each step reads clearly.
On Google Play, your demo video can be the store video. Upload it to YouTube as public or unlisted with ads turned off, then paste the video link into your store listing. Only the first thirty seconds autoplay, so lead with the app, and edit out lines like "download now" or "best" before exporting, because Google Play does not allow that kind of promotional language in the video.
The App Store is stricter. App previews must run fifteen to thirty seconds, use one of Apple's accepted resolutions (886 × 1920 in portrait for current iPhones), and show only screen captures of the app itself, with narration and text overlays allowed on top. Cut a separate App Store preview from your recording to that spec rather than uploading your launch video as is.
Thirty to sixty seconds covers most single-flow demos. Keep social cuts closer to fifteen to thirty seconds and lead with the result. Longer walkthroughs belong in onboarding or help content, where the viewer has already decided to learn the app.
Yes. Upload the recording and Angles turns it into scenes with captions, voice-over, and a call to action. Choose portrait output for phone-first surfaces and landscape for your website, depending on where the demo will run.
A product demo usually starts from a website or product page and explains the whole offer. An app demo starts from the screen: the taps, gestures, and states a user will actually see. If your product lives on a phone or inside a web app, start here. For a broader product explainer, use the AI demo video generator instead.
Yes. Google Play takes a YouTube link for the store video, so upload the export to YouTube as public or unlisted with ads off and add the link to your listing. Keep the strongest part in the first thirty seconds, and remove promotional lines like "download now" or "best" before exporting.
Every Angles account can create finished videos before choosing a paid plan, and editing and previewing in the editor are always free. That is enough to make your first app demo and a few variants before deciding whether you need more.
Related workflow
Turn the same app into short promo cuts, each built around a different reason someone downloads.
Explore related guideStart from a recording of your app and turn one workflow into several launch-ready videos.
Explore related guideCreate a broader product demo from a product page or brief when the story is bigger than one app flow.
Explore related guideUse the launch brief template to clarify the story, or draft your first angle set with the free generator.