The purpose of a screen recording is to show a submission reviewer how to test your app's usage of every Permission and Feature included in your submission. If a reviewer is unable to follow your screen recording and test your app successfully, your submission will be rejected.
Follow these guidelines to ensure that your screen recording includes everything a reviewer needs to test your app successfully.
Our reviewers need to see how an app user logs into your app.
If your app users rely on Facebook Login to grant your app Permissions to access their data, show an app user locating the Facebook Login button and using it to grant your app every Permission that you have included in your App Review submission.
A reviewer will attempt to use Facebook Login and their own test user account to grant your app all of the Permissions in your submission. If the reviewer is unable to grant your app each Permission, your submission will be rejected.
Recommendation: Capture the complete authorization flow, as some permissions require additional confirmation from app users. For example, the pages_manage_engagement permission allows users to select specific Pages to authorize the app to access.
The following screenshots from a sample screen recording show Page selection.
Example — The user logging in with Facebook Login
Example — The user later granting the app access to a Page they manage
For each Permission and Feature in your submission, we recommend that you demonstrate when and how it is being used. Do this by capturing the entire usage flow.
For example, if your app allows app users to publish a Post on a Page, show us how app users can create a Post and how to view it after it has been Published to a Page.
For additional clarity, we recommend that you annotate your screen recording.
Use these best practices as optional tips to consider when recording your screen recording. These tips will help you create a screen recording that clearly demonstrates how your app uses each Permission and Feature in your submission, and can make your screen recording easier for our reviewers to follow.
Before you actually record your screen recording:
Repeating this process a few times helps you identify any areas that are unclear and give you an excellent recording plan, which you can then follow when capturing your actual recording.
Most dedicated screen recording software and video editing software provide tools for adding annotations to your videos. Annotations are text and graphic overlays that allow you to provide notes for specific areas in a video. Annotations are a great way to highlight portions of your recording that show your app using a specific Permission or Feature.
For example, if your app relies on the user_photos Permission, you could use an annotation to point out exactly when your app relies on it to get a user's photos:
We recommend that you use annotations for all of the Permissions and Features that you are requesting. You should be able to find annotation tutorials for your dedicated screen recording software or video editing software online.
If your screen recording contains sections where it can be difficult to see what's happening, consider zooming in to any hard-to-see sections. Most dedicated screen recording apps will allow you to do this after you have recorded your screen recording. If you're not using dedicated screen recording software, you can use video editing software to do it after you have finished recording.
You should be able to find "zoom in" and "zoom out" tutorials for your dedicated screen recording software or video editing software online.
We recommend that you create Test Users and use them in your screen recording recording. Include their credentials with your App Verification Details in your App Review submission so our reviewers can use them to test your app as well. This increases the likelihood that a reviewer can test your app exactly as you depicted in your screen recording.
If your app users are able to create accounts and log in to your app without the aid of Facebook Login, we also recommend that you include test user credentials for one of these users.