Your App Review submission must include a screencast. The purpose of a screencast 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 screencast and test your app successfully, your submission will be rejected.
Follow these guidelines to ensure that your screencast includes everything a reviewer will need to test your app successfully.
Our reviewers need to see how a user signs into your app, so before you start recording, log out of any test accounts you will be using. Be sure to capture the entire Facebook Login flow, from logged-out to logged-in. If your app users can create accounts and log into your app without the use of Facebook Login, capture this flow too.
For example, these screenshots from a sample screencast make it clear that users sign into the app without Facebook Login, but later use Facebook Login to grant the app access to their Facebook data.
A logged-out user before logging in:
The user logging in without the aid of Facebook Login:
The logged-in user attempting to access their Facebook data:
The logged-in user using Facebook Login to connect to their Facebook account:
If your app users rely on Facebook Login to grant your app permissions to access their data, be sure to show a 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 a test user 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.
Make sure to capture the complete authorization flow, as some permissions require additional confirmation from users. For example, the
manage_pages permission allows users to select specific Pages to authorize the app to access.
Here are screenshots from a sample screencast showing Page selection. First, the user loggin in with Facebook Login:
The user later granting the app access to a Page they manage:
For each permission and feature in your submission, demonstrate not only when it is being used, but how it is being used. Do this by capturing the entire usage flow.
For example, if your app allows users to publish a post on a page, show us how to create the post and how to view it after it has been published.
Beginning the post creation process:
Creating the post content:
Publishing the post:
The published post on a page:
Make sure your screencast shows your app using every permission and feature in your submission — if you omit one, it may not be clear to our reviewers how to test it, and your submission will be rejected.
For additional clarity, we recommend that you annotate your screencast.
These are optional tips that you may want to consider when recording your screencast. These tips will help you create a screencast that clearly demonstrates how your app uses each permission and feature in your submission, and will make your screencast easier for our reviewers to follow.
Before you actually record your screencast you should:
Repeating this process a few times will help you identify any areas that are unclear and give you an excellent recording plan.
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 point out exactly when your app uses a specific permission or feature to access data.
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 tat you are requesting. You should be able to find annotation tutorials for your dedicated screen recording software or video editing software online.
If your screencast contains sections where it is 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 screencast. If you are 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 screencast 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 will increase the likelihood that a reviewer will be able to test your exactly as you have depicted in your screencast.
If your app users are able to create accounts and log into your app without the aid of Facebook Login, we also recommend that you include test user credentials for one of these users as well.
If you have access to dedicated screen recording software like Camtasia or Snagit we recommend that you use it. Most dedicated screen recording software provide tools for annotation, zooming, and basic timeline editing so you can polish your screencast, and most offer free trial versions.
If you don't have access to dedicated screen recording software, you can easily use free alternatives such as Quicktime or OBS. These apps don't offer any way for you to annotate, zoom, or edit your recorded video, but you can easily add the recorded video to a free video editor such as iMovie and perform those actions there.