1. SDK Help Center
  2. Effect Construction

How to test AR face filter

Each AR filter requires a unique testing approach with more or fewer actions needed to estimate its performance. Your general filter testing process may cover the following aspects:

Performance iOS, Android

  • Real-time AR face filter — at least 30 FPS on iPhone 5s, 6, 6plus | Samsung s8/Huawei P10/Mi6 and higher

  • AR mask and video recording — at least 30 FPS on iPhone 5s, 6, 6plus | Samsung s8/Huawei P10/Mi6 and higher

User experience

  • You can take a photo or/and video with the effect

  • The effect works stably on the front and rear camera

  • Effects with a distinctive feature which involves user action e.g. trigger, tap, swipe or voice changer have a hint about it (first couple of seconds).

  • The effect works as required with face in the camera, no face, and disappearing face. 

  • You can take a photo or/and video with the effect

  • The effect works stably on the front and rear camera

  • Effects with a distinctive feature which involves user action e.g. trigger, tap, swipe or voice changer have a hint about it (first couple of seconds).

  • The effect works as required with face in the camera, no face, and disappearing face.  

  • Effects with analytics perform correctly (the name of the effect matches, the functional properties match)

  • Effects are stable and perform correctly at different angles (90 degrees rotation, 180 degrees rotation (upside down))

  • Check how the masks stretch on the face (wide open mouth, eyes, grimacing) to make sure that no holes in the mask appear and no element overlap one another

Device compatibility

  • Check effects on Xsmax for crashes (some effects fall on Xsmax)

  • Check effects on Xsmax for incomplete filling of the screen (sometimes the effect does not fill the entire screen with high resolution)