UGC for Apps and SaaS: Formats, Screen Recordings, and Briefs

This guide covers production for software products: the formats, how to set up the demo environment, how creators should capture screens, the privacy rules to put in the brief, where store listings differ from ads, and a brief checklist you can copy.

UGC formats for apps and SaaS

Software has no texture or unboxing moment, so the creator's job is to make a screen feel personal: their problem, their workflow, their moment of relief. These formats do that without needing a big production.

Opening lines matter more in software than almost anywhere else, because the first frame is often a screen the viewer doesn't recognize yet. Start with the creator's face or the problem rather than your dashboard. Our list of UGC hooks organized by angle has opening lines you can adapt.

Set up the demo environment before you brief

Most of the time lost on software UGC goes to access problems: a creator who can't get past onboarding, a paywall, an empty account, or a feature flag that isn't on. Fix those before the first creator receives the brief.

Demo accounts

• Create one dedicated account per creator, so you can turn access off when the project ends and nobody shares a password.
• Pre-unlock everything the video needs: premium tiers, features behind flags, and integrations already connected.
• Decide on onboarding. If the onboarding flow is part of the story, give the creator a fresh account. If it isn't, complete it for them.
• Set an expiry date for the account and the access in the brief, and tell the creator what happens to it after delivery.
• For mobile apps, say exactly which build to install (the public store version or a test build) and how to install it. If the feature isn't released yet, send the test-build invite before filming day.

Test data

An empty dashboard is the most common reason software UGC looks unconvincing. Seed each demo account with fake but realistic data before handing it over:

• Made-up names, companies, and email addresses that clearly aren't real people (use your own test domain).
• Plausible numbers that don't imply results you can't support. A demo revenue chart going up and to the right is an implied performance claim (more on that below).
• Enough history (projects, workouts, transactions, messages) that the key screens look lived-in.
• Avatars and images you have the rights to use, not random photos of people taken from the web.

A click path, not just a feature list

Write the exact sequence of taps or clicks you want on screen. "Show the reporting feature" gives you five different videos. "Tap Reports → This month → Share → Copy link" gives you footage your editor can actually cut.

How creators should capture the screen

Both major mobile platforms have built-in screen recording. On iPhone, Apple's instructions are to open Control Center and tap the Record button. To capture the mic as well, touch and hold the button and turn the microphone on first. Apple also notes that some apps don't allow recording. On Android, Google's instructions are to swipe down twice from the top of the screen and tap Screen record, with options to record audio and to show touches on the screen. Desktop SaaS can be recorded with any screen recorder the creator already uses.

Put these capture settings in your brief:

• Turn on Do Not Disturb or a Focus mode so no notification banners appear during recording.
• Clean status bar: a decent battery level, no personal carrier name or unusual icons where avoidable.
• Light or dark mode: specify one, so videos from different creators match.
• Default font size and display zoom, so the UI looks the way most users see it.
• Slow, deliberate taps with a short pause on each key screen, which gives the editor room to cut and zoom.
• Record the screen separately from the face-cam, then combine them in editing. That gives you a clean screen file to reuse.
• Desktop: close other tabs, hide bookmarks, and record only the app window at a resolution where the text stays readable on a phone.
• Show touches: decide whether you want touch indicators. They help tutorials and look busy in ads.

For delivery formats, file naming, and what to ask for as raw files, use our UGC deliverables checklist, and add one software-specific line to it: deliver the screen recording as its own file.

Privacy: what must never appear on screen

A creator's phone or laptop is full of other people's information, and so is your production database. Make the rules explicit in the brief.

Add a review step for every frame. Scrub the screen recording at slow speed before approving it. Exposed data often appears for only a frame or two, for example during a transition.

Claims in software UGC

Software ads make claims too: "saves me 10 hours a week," "my sales doubled," "the most accurate calorie tracker." The FTC's advertising guidance applies to them the same way it applies to physical products. Advertisers "must have evidence to back up their claims," and implied claims count as well as express ones.

• Time-saved, money-earned, or results claims need evidence, and a creator's personal anecdote isn't the same as evidence of what users generally get.
• Demo data can imply a claim. A dashboard showing a large revenue jump says "this app grew my revenue" even if nobody speaks the words.
• Comparison claims ("faster than [competitor]") need substantiation.
• Health, finance, and similar categories carry extra scrutiny. If your app touches fitness or nutrition, read our guide to claims and compliance for fitness and wellness UGC.

If the creator posts from their own account or gets free premium access, disclosure rules apply as well. See FTC rules for UGC.

Paid social ads vs. app store preview videos

Teams often want one video that works as a TikTok ad and as the App Store preview. That usually isn't possible, because the stores' rules about what a preview may show are much stricter than ad platforms' rules.

Per Apple's own guidelines, a face-cam UGC video isn't an App Store app preview. The screen recording you collected for the UGC project can still become one, as long as it's a clean, separately delivered file. Google Play's guidance focuses on the in-app experience, so the creator's face should play at most a small role there. These rules come from Apple's and Google's developer pages as of October 2026. Check them again before you produce store assets.

For ad specs, use the platform-specific guides: UGC for TikTok ads and UGC for Meta ads.

Choosing creators for software

The best app creators aren't always the most polished on camera. Look for creators who:

• Actually fit your user. A freelancer talking about invoicing software is more believable than a lifestyle creator reading a script.
• Can narrate a screen clearly: slow pace, pointing out what matters, no rambling between taps.
• Own the device you need (iPhone vs. Android, laptop vs. tablet), because screen-recording quality and UI differ by platform.
• Have samples that include a screen recording, or are willing to send a short test clip.

B2B SaaS often needs creators who can believably play a role (an operations manager, a recruiter, a solo founder). Tell the creator in the brief who they're playing and what that person's day looks like.

A worked example of a 30-second app ad

To compare versions of this ad (a different hook, a different first screen), use a simple structure like the one in how to test UGC ad creative.

Brief checklist for apps and SaaS

Add these sections to your standard UGC brief template.

ACCESS
Platform: [iOS / Android / web / desktop]
Build: [public store version / test build - invite sent to EMAIL]
Demo login: sent privately via [CHANNEL] (do not show on screen)
Access expires: [DATE]
Pre-unlocked: [PLAN / FEATURES]
Pre-loaded test data: [WHAT'S IN THE ACCOUNT]

YOUR ROLE
You are: [e.g. a freelance designer who invoices 5 clients a month]
Problem you had before: [ONE SENTENCE]

CLICK PATH (follow exactly, pause 1-2 sec on each screen)
1. [SCREEN] -> tap [BUTTON]
2. [SCREEN] -> tap [BUTTON]
3. [RESULT SCREEN] - hold 3 sec

CAPTURE SETTINGS
- Do Not Disturb / Focus mode ON
- [LIGHT / DARK] mode
- Default text size
- Record screen and face-cam as separate files
- Desktop: app window only, other tabs closed

NEVER ON SCREEN
- Notifications or your personal data
- Real customer data, real people's names or faces
- Card numbers, API keys, admin or internal pages

CLAIMS
You can say: "[APPROVED LINE 1]", "[APPROVED LINE 2]"
Please don't: quote time saved, money made, or rankings
unless listed above; compare to named competitors

DELIVERABLES
- [N] x [LENGTH] vertical 9:16 edits
- Raw screen recording file(s), separate
- Raw face-cam file(s), separate

If you're hiring creators for the first time, how to hire UGC creators walks through sourcing and vetting. On CreatorsUGC (our platform), you can post the brief with this add-on included, and the creators who respond can ask access questions in the on-platform chat before quoting. Send demo logins privately, never in the public brief text. The brands page explains how ordering and payment work.

FAQ

Sources

1. App Previews — Apple Developer
2. Add preview assets to showcase your app — Google Play Console Help
3. Record the screen on your iPhone, iPad, or iPod touch — Apple Support
4. Take a screenshot or record your screen on your Android device — Android Help
5. Advertising FAQ's: A Guide for Small Business — Federal Trade Commission

CreatorsUGC publishes this guide. We run a UGC marketplace, so we have an interest in the topic — we link to independent sources for facts and label illustrative examples.