Filters and effects in the Nosmai Effects SDK

Two ways to create a visual result

Nosmai Effects provides adjustable SDK controls and Cloud Filters.

An adjustable control is a setting the app changes directly, such as a beauty intensity slider. A Cloud Filter is an approved effect selected from the app's cloud catalog and downloaded when required. The app can use either approach or combine them when the platform supports that combination.

Type	Best for	How it is controlled
Adjustable controls	Skin retouching, makeup, face shaping, color, and manual backgrounds	Direct SDK methods and numeric values
Cloud Filters	AR masks, colour looks, frames, particles, 3D content, and backgrounds	Select an approved catalog item, download it, and apply it

A Cloud Filter contains the protected resources and behaviour required for one effect. The SDK validates the download and applies it in the appropriate visual category.

Cloud Filter categories

Category	Purpose	Replacement rule
`filter`	Color, LUT, frame, or general visual filter	Replaces the current regular filter
`effect`	Face-tracked AR effect or mask	Replaces `effect` or `beauty_effect`
`beauty_effect`	Complete authored beauty look	Replaces `effect` or `beauty_effect`
`background`	Authored background experience	Replaces the current background package

Use only the typed catalog values documented by the platform SDK when requesting Cloud Filters.

Delivery

A growing catalog of ready-made filters is available through the Nosmai Asset Store. Filters are not embedded inside the SDK binary or application. The app requests its approved Cloud Filter catalog, downloads the selected item, and reuses the SDK-managed cache when available. Test the exact Cloud Filters used by the application on each target platform.

Runtime parameters

Some Cloud Filters expose named parameters such as intensity, speed, text, or a variant. Read the parameter metadata after applying the filter. Do not guess names or ranges from another filter.

Metadata means information that describes the available controls. It tells the app whether a value is numeric, text, or an option, and whether a range is present. Build controls from that metadata and keep the filter's declared default when the user has not changed it.

Choosing a route

Use direct SDK controls for adjustable camera features. Use Cloud Filters for approved AR effects, authored looks, backgrounds, and frequently changing catalog content.