Spring Physics

Spring physics is Linear's system of treating every UI transition as a physical object with mass, stiffness, damping, and velocity instead of arbitrary timing curves. Elements accelerate, overshoot their resting position by a calculated margin, then decay back with decaying bounces that match real world behavior. Issues created with the C key drop into the list and land with tangible weight. Command bar opens fall from the top like a drawer on rails. Modals scale up then tug back with 8 percent overshoot before settling. The system runs on Framer Motion configs tuned per interaction type. A list reorder needs different stiffness than a toast. Linear refused to soften these values across ten years of pressure. The motion vocabulary ties directly to their keyboard first model, dark canvas contrast, and engineering design unification. It lowers cognitive load because the eye predicts where something will stop and the interface never lies about its physics. The result feels like a machined tool instead of a web page performing animations.

Spring physics is not cubic bezier shortcuts from Tailwind or the default presets in Framer. It is not the wobbly bounce that turns every panel into a rubber ball. It is not slow luxurious easing added to make pitch decks look expensive. Most teams slapping spring labels on their product are running scale and opacity transitions with a fake overshoot at the end. Those break the moment you interrupt them mid flight. Real springs maintain velocity and force across interruptions so a canceled drag snaps back from its current momentum instead of jumping to a new curve. It is not decoration for hero elements while the rest of the app stays stiff. It is not the 450 millisecond version that copies try to pass off as premium. Slowing springs down turns a precision tool into friction. The copies prove it every quarter.

Linear in 2026 shows what disciplined spring physics actually looks like. Hit C and the new issue row springs down from above with stiffness around 480 and damping at 32, overshooting 18 pixels before settling in 170 milliseconds. Rauno Freiberg's 2023 notes on these exact values became required reading for every design engineer. The command bar uses a looser 320 stiffness so it feels like it drops under gravity. Drag and drop reordering chains secondary springs that keep selected cards aligned without fighting the cursor. Plane copied the surface in 2025 but kept SCRUM rituals and their open source Jira backbone. Their springs suggest speed their ceremonies destroy. Shortcut rebranded from Clubhouse in 2023, rebuilt the UI closer to Linear, then slowed their springs to feel enterprise safe. The bounce that should reinforce keyboard triage instead fights their story point rituals. ZenHub layered similar motion over GitHub Issues data shapes so milestones and labels clash with cycle based ergonomics the springs imply. Tability applied the visual layer to an OKR planner where quarterly objectives fight the fast twitch motion. Height post acquisition in 2025 pushed the aesthetic harder yet their original workflow created visible seams every time a spring landed. These five all stole the screenshot. None stole the tuning discipline or the underlying decisions that made the motion feel honest. macOS Big Sur window snapping uses similar springs tuned for trackpad physics and feels invisible until a Windows machine reminds you what stiff tweens actually cost.

Use spring physics when building daily drivers for power users who live in the product eight hours at a stretch. Deploy it for small fast teams of designers, engineers, and product people who ship weekly and value flow state over ceremony. It fits tools like Raycast, Arc, Cursor, or any tracker aimed at teams under thirty that reject heavy process. The motion amplifies retention because leaving the app feels worse than staying inside its physics. It only works when design engineers own the values in production code and can iterate during code review the same way they iterate API contracts. Pair it with keyboard first architecture, technical writing voice, and RFC transparency. The springs then stop being decoration and become another conviction that compounds across the whole product.

Avoid spring physics when selling to large enterprises optimizing for compliance instead of velocity. The bounce that delights a startup CTO reads as instability to a CIO running audit heavy workflows in ServiceNow or Workday. Skip it if your process ends at Figma handoff because the nuance gets lost in translation every single time. Never copy it just because Linear looks good in screenshots. Their springs match a specific taste for speed, written communication, and high trust. Drop those values on a 200 person organization running quarterly planning and the motion lies with every interaction. The worst offenders took Linear's 180 millisecond springs and stretched them to 450 thinking it would feel substantial. They built expensive looking lag that users complain about in every support ticket.

Spring physics turns your interface from a picture of a tool into a tool that happens to live on a screen.