{"id":580,"date":"2026-10-23T15:45:10","date_gmt":"2026-10-23T07:45:10","guid":{"rendered":"https:\/\/en.meishesdk.com\/blog\/?p=580"},"modified":"2026-10-23T15:45:10","modified_gmt":"2026-10-23T07:45:10","slug":"meishe-ar-face-props-2d-and-3d-sticker-sets","status":"publish","type":"post","link":"https:\/\/en.meishesdk.com\/blog\/580.html","title":{"rendered":"Meishe AR Face Props: 2D and 3D Sticker Sets"},"content":{"rendered":"\n

Meishe AR Face Props delivers the sticker capability in two formats \u2014 2D sticker sets and 3D sticker sets \u2014 both anchored to detected facial features, both tracked per frame, and both shipped as content packages your team controls. The two formats serve different creative purposes, and a healthy sticker programme uses both.<\/p>\n\n\n\n

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

Meishe AR Face Props runs on the cross-platform audio\/video processing engine used across the product family, rendering with real-time rendering without pre-processing. It supports face beautification, sticker props, background division, and interactive play, with coverage across iOS, Android, Web, Desktop (Windows), and smart hardware, plus React Native and Flutter through the short-video solution. Sticker sets \u2014 2D and 3D \u2014 are data packages authored in the Asset Creation Platform and published through your own channel.<\/p>\n\n\n\n

2. The two formats<\/h2>\n\n\n\n
Format<\/th>What it is<\/th>Where it shines<\/th><\/tr><\/thead>
2D sticker sets<\/td>Flat stickers and decorations anchored to facial features or applied full-frame<\/td>Fast seasonal volume, graphic styles, brand campaigns<\/td><\/tr>
3D sticker sets<\/td>Dimensional props rendered with real perspective that follow head turns<\/td>Hero campaign moments, premium feel, share-worthy effects<\/td><\/tr>
Gesture triggers<\/td>Recognized gestures switch or launch props<\/td>Hands-free play mid-recording<\/td><\/tr>
Shared anchoring<\/td>Both formats attach to the same detected features<\/td>One library behaves consistently across formats<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Because both formats ride the same detection and rendering pipeline, mixing them in one look \u2014 a 3D crown with 2D sparkles \u2014 costs no additional analysis.<\/p>\n\n\n\n

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

3. Authoring and shipping both formats<\/h2>\n\n\n\n

The content pipeline is format-agnostic from publish onward:<\/p>\n\n\n\n

    \n
  • Designers author 2D and 3D families in the Asset Creation Platform against the same package format the runtime consumes.<\/li>\n\n\n\n
  • A family publishes through your channel like any other content \u2014 no release cycle, no per-format pipeline.<\/li>\n\n\n\n
  • The same package identifier resolves on every platform, so a 3D hero prop works identically on iOS, Android, and Web.<\/li>\n<\/ul>\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: mixing formats in one session.\nimport { createEffectsRuntime } from \"@meishe\/ar-effects\"; \/\/ placeholder name\n\nconst rt = await createEffectsRuntime({ platform: \"android\" });\n\nawait rt.props.attach(\"prop.crown.festival.3d\");   \/\/ 3D hero\nawait rt.stickers.apply(\"sticker.sparkle.gold.2d\"); \/\/ 2D layer<\/code><\/pre>\n\n\n\n
    4. What a sticker calendar looks like<\/h2>\n\n\n\n
    Season<\/th>Format mix<\/th>Why it works<\/th><\/tr><\/thead>
    Launch<\/td>One 3D hero prop plus a 2D everyday set<\/td>Premium first impression with usable daily variety<\/td><\/tr>
    Campaign<\/td>Format matched to the creative<\/td>3D for hero moments, 2D for volume and speed<\/td><\/tr>
    Evergreen<\/td>A rotating catalogue of both<\/td>The library compounds instead of resetting<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    The format pairing is a creative decision the pipeline never constrains: both types publish identically, resolve identically, and verify identically per platform.<\/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>
    Self-developed engine<\/td>The cross-platform audio\/video processing engine used across the product family, refined through years of shipping<\/td><\/tr>
    Both formats, one pipeline<\/td>2D and 3D families author, publish, and resolve identically<\/td><\/tr>
    Real-time, no preprocessing<\/td>Props render from the first camera frame<\/td><\/tr>
    Content as data<\/td>Seasonal families of either format ship without app releases<\/td><\/tr>
    Authoring included<\/td>Designers work in the Asset Creation Platform; Special Effects Customization delivers produced families<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    6. What shipping teams ask first<\/h2>\n\n\n\n
      \n
    • Which format should launch first?<\/strong>\u00a0A 3D hero plus a 2D set covers both first impressions and daily use.<\/li>\n\n\n\n
    • Does 3D authoring require special skills?<\/strong>\u00a0Your designers work in the Asset Creation Platform; for produced 3D families, Special Effects Customization supplies the professional capacity.<\/li>\n\n\n\n
    • How do formats affect QA?<\/strong>\u00a0Each family verifies once per platform regardless of format \u2014 the pipeline does not distinguish after publish.<\/li>\n<\/ul>\n\n\n\n
      A practical authoring note for teams building their first 3D family: keep the hero prop count small and the quality bar high. One crown that tracks beautifully through turns does more for the feature’s reputation than five that track adequately \u2014 and the 2D volume carries daily variety in the meantime. The catalogue grows around proven heroes rather than filling slots for completeness.<\/p>\n\n\n\n
      The review loop rewards the same discipline: a family reviewed on live movement \u2014 turning, leaning, speaking \u2014 ships with confidence that a static-preview review cannot buy. Movement is where anchoring proves itself, so movement is where the review happens.<\/p>\n\n\n\n
      A practical authoring note for teams building their first 3D family: keep the hero count small and the quality bar high. \u2014 and the 2D volume carries daily variety in the meantime.<\/p>\n\n\n\n
      The format pairing stays a creative decision throughout: 3D for hero moments, 2D for volume, and the pipeline never constrains the mix.<\/p>\n\n\n\n
      One pipeline, two formats, every season \u2014 the sticker catalogue grows exactly as fast as the creative team dreams.<\/p>\n\n\n\n
      The format question also has a personnel angle worth naming: 2D families are where new designers ramp \u2014 fast iteration, immediate feedback \u2014 while 3D heroes concentrate the senior craft. A team of any shape finds its division of labour inside one pipeline, and the catalogue reflects the team’s full range rather than its busiest tier.<\/p>\n\n\n\n
      That is the two-format arrangement at its best: structure where it helps, freedom where it counts.<\/p>\n\n\n\n
      The seasonal rhythm also gives the two formats a natural rotation: hero 3D moments anchor the big campaigns, while 2D volume keeps the daily catalogue fresh between them. The pipeline treats both identically, so the rotation is purely a creative cadence decision.<\/p>\n\n\n\n
      The format pairing also keeps budgets honest: 3D heroes carry the wow, 2D sets carry the volume, and neither inflates the other’s cost. The season’s package weight tracks the season’s ambition, not the catalogue’s accumulated history \u2014 a property QA and bandwidth planning both appreciate.<\/p>\n\n\n\n
      Format mix, hero count, campaign pairing \u2014 the creative decisions stay creative, and the pipeline carries them all with the same publish, the same verification, the same day-one arrival on every platform.<\/p>\n\n\n\n
      Two formats, one pipeline, every season \u2014 the 2D\/3D arrangement stays this simple for as long as the catalogue grows.<\/p>\n\n\n\n
      FAQ<\/h2>\n\n\n\n
      Can one look combine 2D and 3D stickers?<\/strong>
      Yes \u2014 both formats anchor to the same detection, so mixing them in one session costs no extra analysis and renders as one composition.<\/p>\n\n\n\n
      Do 3D props behave the same on Web as on mobile?<\/strong>
      Yes \u2014 the same packages resolve on every platform, and the anchoring quality carries across targets.<\/p>\n\n\n\n
      How large is a typical 3D family?<\/strong>
      Small and hero-focused: a few dimensional props per season, complemented by 2D volume, keeps the catalogue premium and the packages light.<\/p>\n\n\n\n
      Can gesture triggers work with either format?<\/strong>
      Yes \u2014 triggers launch or cycle props regardless of format; a wave switches a 3D crown as readily as a 2D sticker.<\/p>\n\n\n\n
      Who owns the sticker catalogue structure?<\/strong>
      Your team \u2014 the Asset Creation Platform holds your structure, and Special Effects Customization can deliver families that fit it.<\/p>\n","protected":false},"excerpt":{"rendered":"
      Meishe AR Face Props delivers the sticker capability in two formats \u2014 2D sticker sets and 3D sticker sets \u2014 both anchored to detected facial features, both tracked per frame, and both shipped as content packages your team controls. The two formats serve different creative purposes, and a healthy sticker programme uses both. 1. Product […]<\/p>\n","protected":false},"author":1,"featured_media":581,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[399,40,10],"class_list":["post-580","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-face-ar-sdk","tag-ar-face-prop","tag-face-ar-sdk","tag-video-editing-sdk"],"_links":{"self":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/580","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=580"}],"version-history":[{"count":1,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/580\/revisions"}],"predecessor-version":[{"id":582,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/580\/revisions\/582"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media\/581"}],"wp:attachment":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media?parent=580"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/categories?post=580"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/tags?post=580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}