Read our examples of instructions and submissions to improve the quality of your App Review submission. You can also refer to our sample submission, which documents a fictitious app review submission for an app that uses Facebook Login.
List your instructions in a step-by-step format so that we can reproduce your action and can use additional properties that belong to the action. All instructions must be in English. Please make sure that you do not:
To tag friends who are cooking with you:
- Click the plus sign below the "I'm making this!" button.
- Select friends.
To add a photo of the recipe you’re making:
- Click the Upload button.
- Select a photo of your food.
A submission that would be approved could use
user_likes to surface personalized and relevant content.
For example, the Sasquatch app explains why the
user_likes permission is needed and how the app uses it to build personalized recommendations:
This second use case would also be approved as long as our review can reproduce this experience where the app has "matches" based on shared likes.
Coco and Etoile Dating App uses the
user_likespermission to match people with common interests. Shared interests are overlapping Facebook
user_likesbetween two people. Each app user can see and remove their interests (Facebook user_likes) from their dating profile.
Please note that using
user_likes to check if someone has liked your app or feature will not be approved. The
user_likes permission provides information on all of a person's likes, and the entirety of this data should be used to enhance the app experience.
You do not need to submit your app if it will only be used by you or by a reduced number of people. Any account listed in the Roles tab in your App Dashboard, such as admins, developers and testers, can access all permissions and generate a user or page access token.
You can use any of these accounts to test your app and create a screencast.
A screencast is a great way to guide us through your app and show us how you're using the requested permissions. Here's some best practices and third party resources for creating a screencast:
Please make sure the version of your app you submit for review loads each time you open it. If we can't load your app, we won't be able to test your app or approve your submission.
The Login button should be easy to find. If we can't log in, we won't be able to test your app or approve your submission.
For example, if your app is using
publish_video, please demonstrate the steps required to post a live video to the app user's timeline..
Only requests the permissions your app really needs. You can see a full list of available permissions on our reference page.
Keep your screencast to 2 minutes or less, if possible.