Skip to main content

Submission and Review Processes

Please review the following before submitting your apps for review:

Submitting for Snap’s Review​

Snap reviews all apps that seek to integrate with Snap Kit prior to enabling integration for public use. After adding an app in the Snap Kit Developer Portal and testing your application in developer mode, you will need to Submit for Review before your integration will be available in the Production Environment. You can test your app in a Developer Environment without approval; but, you must receive approval from Snap in order to release your integration to users.

Please take note of the following tips for a successful review process:

  • Submission fields: Make sure to complete your submission with as much information as possible:
    • The Description field should provide a description of your integration -- What does your app do? Who is it intended for?
    • The Integration Description field should include information on how you will use each Kit. For example, if you are applying for Creative Kit, you could describe the sticker you intend to create for Snapchatters to share on Snapchat.
  • Monetization: Monetizing your integration is permissible only with prior approval. Please Contact snapkit-support@snap.com with the following information to request a custom monetization agreement.
  • URL attachments: URL attachments are only allowed for select developers and for pre-approved use cases. To be considered for this feature, you must describe each use in detail, including the content Snapchat users will be linked to.
    • Examples of URL attachments we may approve include the sharing of news articles, music, long-form video, donations, polls and RSVPs.
    • We strictly prohibit abusive uses of CK URLs, including but not limited to: direct app downloads, friend graph recreation and automatic link-outs from Snapchat to 3rd party applications.
    • Any abuse of URL attachments will result in the feature being turned off for the app and can result in the app being removed from the Snap Kit program.
  • Integration video: Ensure the submitted integration video highlights how your integration works (i.e. if you are applying for Creative Kit, make sure that your video shows the use of Creative Kit). If you are applying for multiple Kits, make sure that your integration video highlights how you intend to use each Kit.
  • Choosing the right Kit: Be thoughtful about what Kits you are applying for! In addition to your video that shows the integration for your requested Kit(s), make sure to apply for Kits that make sense for your app.
  • Privacy Policy requirement: Include a link to your app’s Privacy Policy. Links to another company's Privacy Policy or Snap Inc.'s Privacy Policy will not be accepted.
  • Snap brand protection: Don’t incorporate any of Snap’s trademarks or brand indicia into your integration or integration title, except for informational references. This includes, but is not limited to using SNAP or SNAPCHAT, the Ghost Logo, the same yellow color, or mimicking the Snapchat UI.

Review Process​

When you submit your integration for review, please provide as much relevant information as possible. Screen recordings, visual aids, and detailed descriptions will help get your integration through the review process quicker. (If your app is not yet launched, please describe your app and how you plan to use the requested Kit(s) in as much detail as possible, including a screen recording of your integration working in a staging environment, an intended launch time frame, and if the app's sole use is for a Snap Kit integration in the description.) We aim to have all integrations reviewed in one to two business days, however depending on your integration’s category or the type of content in your integration, we may require additional information and review times could be longer.

We understand that your app may change over time. In the case that your app's functionality changes significantly or in a way that may affect its compliance with the App Review Guidelines, please re-submit your app for review. Apps are periodically and randomly selected to be re-reviewed. If you misrepresent your intended use of Snap Kit, or the way you use it changes after our initial review, we reserve the right to revoke API access. When non-compliant, you'll be required to make the outlined changes or will be subject to suspension.

For compliance issues not related to community safety or privacy, you will be notified by email and given 2 weeks to resubmit your application for re-review. For issues that have the potential to impact community safety or privacy, the app's access to the Snap Kit platform may be immediately revoked in an abundance of caution. When you resubmit an updated version of the app, it will be re-reviewed and if compliant, the app may be reinstated.

Top 4 Reasons for Rejection​

It's important to fill out your integration application with as much information as possible so that our review team is properly able to assess your integration. Common rejection reasons include:

  • Lack of an integration video or unclear Kit use case from the integration video, e.g. there is no submitted integration video or the submitted integration video does not highlight the purpose of your app.
  • Missing Information, e.g. a link to your app’s Privacy Policy was not included at submission.
  • Kit Mismatch, e.g. the integration video does not show how the Kit you are applying for would be used
  • Snap Trademark Issues, e.g. the name of your app.

Questions about these guidelines and the integration approval process can be sent to snapkit-support@snapchat.com.

Submitting to Apple​

After you've created your app in the Snap Kit developer portal, developed it using the SDKs, and reviewed all the necessary guidelines and checklists, you will need to submit your app to Apple. Learn how to complete the final building and publishing phase below.

Including the Framework Thinning Script in Your Build​

The Snap Kit SDK contains fat frameworks that have both simulator and device binaries. Before submitting to Apple, the simulator binaries must be stripped out. Copy the code block below and paste the code as a run script in the Build Phases of your target.

Make sure you put it after the embed frameworks phase and set it to use /bin/sh. Otherwise, you’ll see an error about unsupported architecture.

APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"

# This script loops through the frameworks embedded in the application and
# removes unused architectures.
find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
do
    FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
    FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
    echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"

    EXTRACTED_ARCHS=()

    for ARCH in $ARCHS
    do
        echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
        lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
        EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
    done

    echo "Merging extracted architectures: ${ARCHS}"
    lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
    rm "${EXTRACTED_ARCHS[@]}"

    echo "Replacing original executable with thinned version"
    rm "$FRAMEWORK_EXECUTABLE_PATH"
    mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"

done

If you’re having trouble, you might find it helpful to read about stripping unwanted architectures from dynamic libraries in Xcode.

Was this page helpful?
Yes
No