After Xingliu's platform migration, returning users aren't asking "what features
disappeared" — they're asking where familiar actions moved and how the
interaction syntax changed. This guide motion answers one thing: how Object Mark
works, how marks enter the chat, and how two tagged objects become a single
executable edit command.
Three Questions the Guide Must Answer
What marking is. Two reference images sit side by side on the canvas — a
product shot and a figure shot. The user drops blue mark pins on the shoe and
the foot; the system reads each region and surfaces label candidates.
How marks enter chat. Thumbnails and numbers appear at the bottom of the
chat input, progressing from generic "image1 / image2" to "1 Shoes" and "2 Feet"
— making clear that marks aren't decoration; they're reference variables.
How marks drive editing. Typing "Put this [1 Shoes] on the [2 Feet]" embeds
both marks into a natural-language instruction and completes a cross-image
object transfer. The full chain from tap to result needs no extra explainer
panel.
Production Notes
One operation chain, no segments. Unlike Lovart's five-part onboarding,
migration users already have baseline context — they only need the new syntax
walked once. Motion follows pin → recognize → name → reference → execute, with
the camera locked on canvas–chat linkage throughout.
UI state before copy. Visual feedback lands first when a pin drops; chat
updates follow after labels appear. The Object Marked dropdown shows only
necessary options to avoid overload. English and Chinese versions share the same
AE timeline with text-layer swaps only.
Hold on the instruction. Before the final composite appears, the complete
prompt in the input field holds for a beat so viewers can read the
mark-to-language mapping, then cut to the result to close.
Overall production & compositing by @Leo Wang