The desk is the whole stage
and it is one arm away
A desktop robot is not a shrunken humanoid. It is seen, touched and heard within an arm's reach, so motion, sound and expression have to be designed together. Screen desk pets, single-arm desktop assistants and desk monitoring units are three builds with three cost bands.
Three builds
three cost bands
Decide whether it moves, how many joints it has, and whether it has a face. Those three answers set the cost and the schedule.
Motion is its language
not a number on a spec sheet
On a desk the user is one arm away. Too fast reads as a toy, too slow reads as broken, too loud reads as cheap.
A joint is not a number. Each one adds structure, wiring, calibration and a failure point, and the motion script gets rewritten. Work back from the motion script to the joints, not the other way round.
A desk device sits close to the ear. Gear whine, plastic resonance and base vibration all read as cheap. Gear ratio, helical teeth, damping pads and wall thickness are fixed at prototype stage; after tooling they are not adjustable.
Constant-velocity straight moves look like an industrial arm, not a creature. Keyframes with ease-in and ease-out, plus slight overshoot on a turn, are the whole secret, and they cost nothing in motor price.
People read a face faster than a movement. The expression lands a fraction of a second early and the mechanism follows, and the whole thing reads as one reaction. Reverse it and even good motion feels sluggish.
A desk arm can reach a cup, a pen, a finger. Torque limits, stall detection, joint end stops and compliant stop belong in firmware, not only in the mechanical stops.
Idle state gives a device away: perfectly still looks like a brick, random motion looks like a fault. Breathing micro-moves, an occasional glance up, and a full reaction only when called: that idle script is its own design task and its own power test.
Where mass production breaks
six things a prototype hides
With something that moves, almost every yield problem is a unit-to-unit difference.
Who this line fits
| You are | What we take | Starting point |
|---|---|---|
| Cross-border seller | rebranded unit + white-label app + packaging languages + certification support | form and motion script |
| IP or content owner | character turned into expressions and motion, voice and script execution | character set and motion list |
| Desktop tool brand | single-arm structure + firmware + desktop app linkage | motion needs and joint count |
| Brand with its own hardware team | PCBA + firmware + cloud, you run unit and structure | board and joint spec confirmation |
MOQ, lead time and price move with model and configuration and are confirmed line by line at quotation; this page is not a quotation offer.
Motion script first, joints second
Sixty percent of a desktop robot quote comes from joint count and the screen. Tell us in one sentence what it should do and who watches it, and we can quote a cost band.