Building sticker sets with the Face AR SDK is a content workflow, not an engineering project: designers author in the Asset Creation Platform, the SDK consumes the packages, and your channel delivers them to every platform the product ships on. A first family goes from concept to live catalogue in days.
1. Product Positioning
The Face AR SDK serves props and stickers from the family’s cross-platform audio/video processing engine — real-time, no preprocessing. Targets include iOS, Android, Web, Desktop (Windows), and smart hardware, with React Native and Flutter via the short-video solution. Sticker sets ship as data packages — authored once, resolved everywhere, updated without app releases.
2. The build workflow
| Step | What happens | Who does it |
|---|---|---|
| 1. Plan the family | Choose formats (2D, 3D, mixed) and the campaign theme | Product and design |
| 2. Author | Build the stickers in the Asset Creation Platform against the package format | Design |
| 3. Review | Check anchoring, tracking, and look on target devices | Design and QA |
| 4. Publish | Release the family through your delivery channel | Content ops |
| 5. Read | Watch engagement per set and plan the next family | Product |
No step involves an engineering ticket after the runtime is integrated once — that is the structural property that keeps sticker programmes fast.
3. What good families have in common
Launch catalogues that perform share three habits:
- A hero moment and daily volume. One premium 3D prop gives the family its screenshot; a 2D set gives users something to change daily.
- Anchoring checked on real movement. Review happens on live camera sessions — turning, speaking, leaning — because that is where users meet the sticker.
- A naming convention from day one. Identifiers set in the first family keep the tenth family’s catalogue navigable and its analytics clean.
The snippet below is schematic. Names and signatures are illustrative, not the shipped API.
// Illustrative: applying a family the design team just published.
import { createEffectsRuntime } from "@meishe/ar-effects"; // placeholder name
const rt = await createEffectsRuntime({ platform: "android" });
await rt.assets.resolve(["family.festival.02"]);
await rt.props.attach("family.festival.02/crown");
await rt.stickers.apply("family.festival.02/sparkle");4. Publishing and growing the catalogue
After review, the family publishes through your channel and resolves on every platform simultaneously — there is no per-platform variant to maintain and no release train to catch. Seasonal families stack into an evergreen catalogue: last season’s assets keep working, engagement data shows which sets earn their slot, and the library compounds instead of resetting each quarter.
When a season needs professional capacity beyond the in-house team, Special Effects Customization delivers produced families that land in the same pipeline — same format, same publish path, same catalogue.
5. Why teams choose Meishe
| Advantage | What it means for your project |
|---|---|
| Self-developed engine | The cross-platform audio/video processing engine used across the product family, refined through years of shipping |
| Designer-led authoring | The Asset Creation Platform matches the runtime’s package format exactly |
| Content as data | Families publish without app releases, on your schedule |
| Cross-platform resolution | One publish serves every platform the product ships on |
| Special Effects Customization | Produced families available when a season needs extra capacity |
6. What shipping teams ask first
- How long does a first family take? Days, not weeks — authoring and review dominate, and both happen in the design toolchain.
- What does QA verify? Anchoring and tracking on your target devices, in live sessions — the render parity across platforms is the engine’s work.
- How do we staff seasonal peaks? In-house authors cover the calendar; Special Effects Customization absorbs the spikes.
A note on catalogue hygiene that pays off quietly: retire underperforming sets on the same cadence you publish new ones. A library that only grows becomes noise; a library that curates becomes a destination. The publish channel makes retirement as cheap as launch — one operation, no client work — so the catalogue reflects intent rather than accumulation.
Teams that run this discipline report the same outcome: engagement concentrates on families users actually want, the next season’s plan writes itself from data, and the sticker feature reads as curated rather than dumped.
The workflow, end to end, is the quiet pitch of the whole capability: plan, author, review, publish, read — five verbs, zero engineering tickets, repeatable every season.
Plan, author, review, publish, read — then repeat next season, better.
For product managers, the workflow’s five verbs convert directly into planning artifacts: the season plan is a list of families, the review is a checklist on real movement, the publish is a calendar entry. Nothing in the sticker programme requires translating between content language and engineering language — the pipeline speaks one dialect end to end.
Five verbs, one dialect, every season — that is the pipeline’s promise, kept.
Finally, the workflow scales down as gracefully as it scales up: a single designer with a seasonal slot runs the same five verbs a ten-person studio runs. The pipeline’s shape does not change with headcount — only the volume does.
The last hidden benefit is institutional: the workflow documents itself. Five verbs, one platform, one channel — a new team member’s onboarding for the sticker programme is a walkthrough, not a manual, because the pipeline has no secret corners to explain.
Five verbs, one platform, one channel — the sticker programme in eight words, running every season.
One more sentence for the planning doc: the sticker programme’s cost curve is flattest in the content family of any camera feature — the first family pays for the learning, and every family after that pays only for its own art.
Plan, author, review, publish, read — then repeat next season with a richer catalogue and a wiser calendar. The workflow is the programme; the programme compounds.
The five-verb workflow scales with the team and the calendar alike: more designers, more families, same process, same publish path.
And the habit the workflow builds extends past the design team: product reads the analytics, ops reads the publish log, QA reads the review notes — one shared vocabulary around five verbs that everyone in the room can recite by season two.
FAQ
Do stickers require engineering involvement after integration?
No — authoring, review, and publishing all happen on the content side; the runtime resolves whatever the channel delivers.
Can we test a family before it goes public?
Yes — publish to a staging channel and verify on real devices; the production publish is then a channel operation.
How do sticker analytics work?
Sets are identifiers, so engagement maps cleanly per family and per item — the catalogue becomes measurable in its own structure.
What if a sticker needs a fix after launch?
Edit in the Asset Creation Platform and republish — the correction reaches every platform in one publish.
Can families target specific markets or cohorts?
Yes — the channel is yours, so a family can publish to a region or cohort exactly like any content you deliver.