{"id":529,"date":"2026-10-23T14:51:44","date_gmt":"2026-10-23T06:51:44","guid":{"rendered":"https:\/\/en.meishesdk.com\/blog\/?p=529"},"modified":"2026-10-23T14:51:44","modified_gmt":"2026-10-23T06:51:44","slug":"ar-face-prop-beautification-stickers-and-background-division-in-one-sdk","status":"publish","type":"post","link":"https:\/\/en.meishesdk.com\/blog\/529.html","title":{"rendered":"AR Face Prop: Beautification, Stickers and Background Division in One SDK"},"content":{"rendered":"\n

AR Face Prop is Meishe’s all-in-one interactive solution: face beautification, sticker props, background division, and other interactive play types in a single SDK. Instead of assembling a beauty engine from one vendor, stickers from another, and segmentation from a third, your product gets the full effect set from one engine, one integration, and one content pipeline.<\/p>\n\n\n\n

1. Product Positioning<\/h2>\n\n\n\n

AR Face Prop runs on the cross-platform audio\/video processing engine used across the product family, with real-time rendering without pre-processing. It supports face beautification, sticker props, background division, and other types of features, providing a variety of interactive play. The platform set covers iOS, Android, Web, Desktop (Windows), and smart hardware; React Native and Flutter join via the short-video solution. It is a layer for your own app \u2014 the camera UI, permissions, and upload flow remain yours.<\/p>\n\n\n\n

2. What is in the box<\/h2>\n\n\n\n
Capability<\/th>What it does in your app<\/th><\/tr><\/thead>
Face beautification<\/td>Skin smoothing, face reshaping, and makeup applied live in the camera preview<\/td><\/tr>
Sticker props<\/td>2D and 3D stickers anchored to detected facial features \u2014 glasses sit on the nose, crowns sit on the head, 3D props follow head turns<\/td><\/tr>
Background division<\/td>Real-time separation of subject and background, so users change scenes without a green screen<\/td><\/tr>
Interactive play<\/td>Gesture-triggered effects and responsive props \u2014 a raised hand starts an effect, a wave switches the sticker<\/td><\/tr>
Filters<\/td>Colour-grading filters with adjustable intensity alongside the AR features<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

All capabilities read from one detection result per frame. A user wearing beautification, a 3D sticker, and a replaced background generates one face analysis \u2014 the frame budget stays close to flat as the visible effect set grows.<\/p>\n\n\n\n

\"AR<\/a><\/figure>\n\n\n\n

3. Why one SDK instead of three<\/h2>\n\n\n\n

Assembling effects from multiple vendors works on paper and hurts in production:<\/p>\n\n\n\n

    \n
  • Three integrations become three maintenance tracks<\/strong>\u00a0\u2014 each update, each platform port, each device quirk handled separately.<\/li>\n\n\n\n
  • Effects from different engines never quite match<\/strong>\u00a0\u2014 detection timing and rendering paths differ, and users notice on close inspection.<\/li>\n\n\n\n
  • Content pipelines fork<\/strong>\u00a0\u2014 three authoring flows, three delivery mechanisms, three release rhythms.<\/li>\n<\/ul>\n\n\n\n

    One SDK turns that into one of each: one integration on one engine, one consistent render, one content pipeline in the Asset Creation Platform. Campaigns ship as packages that every capability picks up simultaneously.<\/p>\n\n\n\n

    \n

    The snippet below is schematic. Names and signatures are illustrative, not the shipped API.<\/p>\n<\/blockquote>\n\n\n\n

    \/\/ Illustrative: beautification, a 3D prop, and background division together.\nimport { createEffectsRuntime } from \"@meishe\/ar-effects\"; \/\/ placeholder name\n\nconst rt = await createEffectsRuntime({ platform: \"ios\" });\n\nawait rt.looks.apply(\"look.natural.01\");           \/\/ beautification\nawait rt.props.attach(\"prop.crown.party.3d\");      \/\/ sticker prop\nawait rt.segments.setBackground(\"scene.confetti\"); \/\/ background division<\/code><\/pre>\n\n\n\n
    4. Interactive play that keeps users in the camera<\/h2>\n\n\n\n
    The interactive layer is what turns an effects feature into a product loop. Gesture detection gives hands the controls \u2014 raise to start, wave to switch, clench to advance a template step. Props respond to the face they are attached to, and because gesture detection shares the same per-frame analysis as the other effects, adding interaction adds no second detection pass.<\/p>\n\n\n\n
    For product teams, this is the difference between a camera users visit and a camera users stay in: effects that respond, in real time, on every platform the product ships on.<\/p>\n\n\n\n
    5. Why teams choose Meishe<\/h2>\n\n\n\n
    Advantage<\/th>What it means for your project<\/th><\/tr><\/thead>
    All-in-one coverage<\/td>Beautification, stickers, background division, and interactive play from one SDK \u2014 no vendor assembly<\/td><\/tr>
    Self-developed engine<\/td>Meishe’s own cross-platform audio\/video processing engine, developed and refined in-house across the product family<\/td><\/tr>
    Real-time, no pre-processing<\/td>Effects the moment the camera opens<\/td><\/tr>
    Small footprint<\/td>A small core; optional modules on demand<\/td><\/tr>
    Content pipeline included<\/td>Asset Creation Platform for in-house authoring; Special Effects Customization for produced collections<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    6. What shipping teams ask first<\/h2>\n\n\n\n
      \n
    • Which parts of AR Face Prop do we enable first?<\/strong>\u00a0Whichever matches your launch feature set \u2014 the rest are modules you switch on later from the same library.<\/li>\n\n\n\n
    • Does the interactive layer need its own integration?<\/strong>\u00a0No \u2014 gesture detection is part of the same stack and shares the same detection pass.<\/li>\n\n\n\n
    • Who builds our sticker library?<\/strong>\u00a0Your designers in the Asset Creation Platform, or Meishe’s Special Effects Customization service for produced collections.<\/li>\n<\/ul>\n\n\n\n
      Your product<\/th>What AR Face Prop covers<\/th><\/tr><\/thead>
      Social camera app<\/td>Beautification and sticker props as the daily core; seasonal campaigns as packages<\/td><\/tr>
      Commerce and try-on flows<\/td>Beautification plus segmentation for clean product focus<\/td><\/tr>
      Education and community apps<\/td>Interactive play that keeps sessions in the camera<\/td><\/tr>
      Enterprise capture tools<\/td>Background division for professional framing without studio setup<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Each row uses the same SDK and the same content pipeline \u2014 the difference is which modules you enable first and which packages your designers author.<\/p>\n\n\n\n
      However the product plan starts, the SDK investment compounds in one direction: more packages, more platforms, more play \u2014 same engine, same pipeline.<\/p>\n\n\n\n
      The same compounding applies to campaigns: each seasonal package builds on the assets and conventions of the last, so the library gets richer while the effort per campaign stays flat.<\/p>\n\n\n\n
      Between launch and the second year, the pattern holds: every capability you switch on later \u2014 segmentation, gestures, a new sticker family \u2014 joins a stack your team already operates.<\/p>\n\n\n\n
      The practical starting move is small: enable beautification and one sticker family, publish a first campaign through your own channel, and read the engagement numbers. Everything after that \u2014 background division for a commerce push, gesture triggers for a community feature, a 3D prop line for a seasonal event \u2014 is a module switch and a package publish on a stack the team already knows.<\/p>\n\n\n\n
      That is the quiet advantage of the all-in-one arrangement: growth never requires a re-platforming decision, because the capabilities you grow into were present from the first integration. The SDK you linked on day one is the SDK running your second-year flagship campaign.<\/p>\n\n\n\n
      And because every campaign lands as data, the operating cost of staying ambitious stays low: a bigger library is more packages to curate, not more code to maintain.<\/p>\n\n\n\n
      FAQ<\/h2>\n\n\n\n
      Can we start with just beautification and stickers?<\/strong>
      Yes. Background division and interactive play are modules you enable when the roadmap calls for them \u2014 same SDK, same packages.<\/p>\n\n\n\n
      Do 3D props run on every platform?<\/strong>
      Yes \u2014 2D and 3D sticker sets are part of the shared capability set, resolving on every covered platform from the same packages.<\/p>\n\n\n\n
      How does background division work without a green screen?<\/strong>
      Segmentation runs in real time on the camera frame, separating subject from background as part of the same rendering stack \u2014 no physical setup, no manual masking.<\/p>\n\n\n\n
      Can effects respond to more than gestures?<\/strong>
      Props anchored to facial features respond to head movement, and gesture events trigger actions \u2014 the interactive vocabulary covers the common camera-app patterns.<\/p>\n\n\n\n
      What does an update to our sticker library involve?<\/strong>
      Packages are data: publish through your own channel and every platform picks up the new content \u2014 the app binary stays untouched.<\/p>\n","protected":false},"excerpt":{"rendered":"
      AR Face Prop is Meishe’s all-in-one interactive solution: face beautification, sticker props, background division, and other interactive play types in a single SDK. Instead of assembling a beauty engine from one vendor, stickers from another, and segmentation from a third, your product gets the full effect set from one engine, one integration, and one content […]<\/p>\n","protected":false},"author":1,"featured_media":530,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,6],"tags":[399,402,400,374,401],"class_list":["post-529","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-face-ar-sdk","category-video-editor-sdk","tag-ar-face-prop","tag-background-division","tag-beautification","tag-sdk","tag-stickers"],"_links":{"self":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/529","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/comments?post=529"}],"version-history":[{"count":1,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/529\/revisions"}],"predecessor-version":[{"id":531,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/529\/revisions\/531"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media\/530"}],"wp:attachment":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media?parent=529"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/categories?post=529"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/tags?post=529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}