loading code fetching the highlighted snippet
useTime(key) returns the same motion value for every caller passing the same key. Two independent components stay locked in phase without a shared store — perfect for orchestrating ambient motion across disjoint subtrees.
useTime('synced-timeline'). Motion looks the key up
in a registry — first call creates the clock, every subsequent call gets the same
store. Identical ticks, no prop-drilling.useTime()) for a per-component clock when you want
independence. Use a key when you want different parts of the page — different
routes, even — to share a heartbeat.