Motion in UI Design: Movement That Serves the Next Tap

Motion in a product UI should explain what just happened: a row saved, a sheet opened, a payment confirmed. A looping hero video on 4G is not motion design. It is a bounce with a soundtrack.

CodeLoop Studio in Sarajevo draws UI for the site or app the same team ships. Design-with-build is web design with a build. The English UI/UX service page is UI/UX. This note is when we animate, and when we refuse.

Movement that earns its milliseconds

Loading, empty, error, success — those states need a cue. A booking site such as More than Lashes needs a form that feels finished, not a parallax intro. Koliko on a shift needs the count to update. Guests on a phone do not wait for a three-second logo sting.

A landing with one job should stay still enough to tap — landing pages. A shop checkout should not animate the total while the thumb is on pay — ecommerce checkout.

What we freeze

• Prefer reduced motion. OS settings are not a nice-to-have. We respect them.

• Phone first. If the animation stutters on a mid-range Android, it is out. Device QA is part of custom mobile app development.

• No trend for its own sake. Glass and spring physics on a clinic site are how people miss the phone number. Clinic websites stay readable.

• Same team codes it. A Figma prototype with motion we cannot implement is a moodboard. We will not sell that as delivery.

What we will not ship

Auto-playing sound. Full-screen video as the only H1. Micro-interactions that delay a legal form. If you need a brand film, hire a studio that makes films. We make screens that get used.

Send the screen that must move

Which state change is unclear today, and on which device you tested. Reply in 24 hours — online estimate or contact.