Immediate Feedback
Every action acknowledged, so nothing feels ignored.
Interaction Design Services
Interaction Design Services for What Happens Between Click and Result
Static designs describe two moments: before an action and after it. Everything in between — the feedback, the waiting, the transition, the failure — is where users decide whether the software is working. Interaction design services cover that gap, which is usually left to defaults.
We Design the In-Between
The moment after a click is where confidence in software is won or lost.
Waiting Made Legible
What is happening and roughly how long.
Motion With Purpose
Transitions that explain a change, not decorate it.
Failure Handled
What happens when the action does not succeed.
Reduced Motion Respected
For anyone who has asked for less of it.
What interaction quality is judged on
Interaction design is about what happens between states — how the interface responds, how long it takes, and whether the user can tell what is going on. All of it is observable, and all of it is checkable against the same criteria on any product.
Input acknowledgementWhether every action produces immediate visible feedback
System statusWhether the user can tell what the interface is doing and how long it will take
Motion purposeWhether each animation communicates something or merely decorates
DurationWhether transitions are fast enough not to obstruct repeated use
Reduced motion supportWhether the interface respects the user’s stated preference
ReversibilityWhether an action can be undone rather than only confirmed
Error preventionWhether invalid actions are prevented rather than rejected afterwards
Focus behaviourWhere keyboard focus moves when content changes
Change announcementWhether dynamic updates are conveyed to assistive technology
Touch target sizingWhether controls are usable without precision pointing
Reduced motion is a stated user preference, not a nice-to-have. For people with vestibular conditions, large parallax and sweeping transitions can cause genuine physical symptoms, and the operating system already communicates the preference — ignoring it is a deliberate choice rather than an oversight.
Interaction Design, Explained
What Happens After a Click?
Four moments, each of which needs a decision.
Discuss Your Product →- 1
Acknowledgement
Immediate, so the user knows the click registered.
- 2
Progress
What is happening, if it takes more than a moment.
- 3
Result
What changed, made visible rather than assumed.
- 4
Failure
What to do, if it did not work.
What Interaction Design Covers
Feedback, motion and the states between actions and outcomes.
The full state matrix is covered by web app UX design. The full state matrix these behaviours live inside is web app UX design; consistency across features is design systems.
How We Design Interactions
Enumerate the actions, then design what each one produces.
List the Actions
Everything a user can do.
Define Feedback
What acknowledges each one, immediately.
Design the Waiting
For anything not instant.
Handle Failure
Including what happens to unsaved work.
Specify It
Timing and easing, so the build matches the intent.
Where interaction detail earns its cost
Interaction work matters most where actions are frequent, where consequences are significant, or where the interface has to compensate for something slow. Elsewhere it is refinement.
High-frequency interfaces
Where an action is performed hundreds of times a day and every unnecessary confirmation or animation is multiplied accordingly. Here the objective is usually removing interaction rather than adding it.
Interfaces with unavoidable waiting
Where operations genuinely take time and the interaction has to make the wait comprehensible. Progress that indicates what is happening and how much remains changes the experience without changing the duration.
Complex or destructive operations
Where a mistake is costly and the design has to make consequences visible before commitment. Reversibility is almost always better than confirmation, because it does not rely on the user reading anything.
Touch and mobile-first products
Where gesture, target size and immediate feedback carry more weight than on a pointer-driven interface. Gestures without visible alternatives are the recurring accessibility failure in this category.
Products where responsiveness is the differentiator
Where competitors are functionally similar and the experience of using the product is what distinguishes it. This is where interaction work has commercial rather than merely qualitative value, and it should be built into the design system so it stays consistent.
Feedback
Why the Unacknowledged Click Causes Duplicates
A user who is not told their action registered assumes it did not.
What does no feedback produce?
A second click. Then possibly a third. If the action creates something — an order, a message, a payment — the user has now created it several times.
The fix is trivial: the control changes state on press, immediately, before the result is known. It costs nothing and it removes an entire class of support incident.
It is left out because the developer testing it has a fast connection and a local server, so the result appears instantly and the gap never exists.
When does motion help?
When it explains a spatial relationship: a panel sliding from the edge it will return to, an item animating to the place it was filed, a modal growing from the control that opened it.
It stops helping when it is decorative or slow. Anything above roughly a third of a second in an interface people use repeatedly becomes a delay rather than an explanation.
And it must be reducible. Motion that cannot be turned down causes genuine discomfort for some users, and honouring that preference is a single media query.
Feedback is the whole job
Nearly every interaction problem reduces to the interface failing to tell the user what is happening. A button that does not visibly react leaves the user unsure whether their tap registered, so they tap again. An operation with no progress indication is indistinguishable from a frozen screen. A save with no confirmation leaves someone checking whether their work persisted.
The remedy is consistent and unglamorous: acknowledge input immediately, indicate ongoing work, confirm completion, and explain failure. None of this requires elaborate motion. A state change on press, a progress indicator, and a brief confirmation cover most of it.
This is also where perceived performance is won. Users judge speed by responsiveness rather than by elapsed time, so an operation that acknowledges input instantly and completes in two seconds feels faster than one that shows nothing and completes in one.
Motion should carry meaning
Animation is worth its cost when it explains something: where an element came from, what relates to what, that a list has reordered rather than replaced its contents. Motion used this way reduces cognitive effort, because the user does not have to reconstruct what changed.
Motion that exists to decorate has the opposite effect over time. It is charming on first encounter and an obstruction by the hundredth, because it sits between the user and the thing they were trying to do. The relevant question for any transition is whether removing it would make the interface harder to understand.
Duration matters as much as presence. Transitions long enough to be appreciated in a demonstration are usually too long for repeated use, and the appropriate length for a frequently repeated action is shorter than it feels while designing it.
Undo beats confirmation
The default response to a destructive action is a confirmation dialogue. It is easy to implement and it works poorly, because users learn to dismiss dialogues reflexively — the prompt appears in the same place every time and becomes an obstacle rather than a decision point.
Allowing the action and offering a way back is generally more effective. The user is not interrupted, the common case is fast, and the rare mistake is recoverable. It also handles the case a confirmation cannot: someone who genuinely intended the action and immediately realises it was wrong.
Confirmation remains appropriate where undo is genuinely impossible — money that has left an account, a message that has been sent, a record a regulator requires to be permanent. Reserving interruption for those cases is what keeps it meaningful when it appears.
Questions, answered.
Interaction design services cover what happens between an action and its result — feedback, loading states, transitions, micro-interactions and failure behaviour.
Because nothing acknowledged the first click. The control should change state on press, immediately, before the result is known — it costs nothing and prevents duplicate submissions.
Where it explains a change — something arriving from a place, returning to a place — it helps. Decorative motion mostly adds delay, particularly in software people use repeatedly.
Short. Above roughly a third of a second, motion in a frequently used interface reads as a delay rather than an explanation.
Honour it. Some users experience genuine discomfort from animation, and respecting the preference is a single media query with a static alternative.
UI design concerns what the interface looks like in a given state; interaction design concerns what happens between states — response to input, transitions, timing, feedback and error handling. A well-designed static screen can still be poor to use if what happens when you touch it is unclear or slow.
Purposeful motion is genuinely useful: it shows relationships, indicates progress and makes state changes comprehensible. Decorative motion is optional and frequently harmful with repetition. The distinction is whether removing it would make the interface harder to follow — if not, it is costing time on every use for no benefit.
Acknowledgement of input should be immediate, since anything perceptible reads as unresponsive. For the operation itself, what matters is whether the user knows something is happening and roughly how long it will take. A slow operation with clear progress is tolerable; a fast one with no feedback frequently is not.
They are efficient for people who know them and invisible to people who do not, so they should be shortcuts rather than the only route. Every gesture needs a discoverable equivalent — a visible control or menu item — otherwise the capability is inaccessible to new users and to anyone using assistive technology.
Directly and substantially. Focus has to move sensibly when content changes, dynamic updates have to be announced rather than only shown, motion has to respect the reduced-motion preference, and nothing important can depend on a gesture or on colour alone. These are interaction decisions, and getting them wrong makes a product unusable for people who cannot compensate visually.
Still deciding if interaction design services is right for you?
Talk to UsThe Developer Had a Local Server
Feedback on a button press gets skipped for a specific and understandable reason: on the developer's machine, the result appears instantly. There is no gap to fill.
On a phone, on a mobile connection, with a server under load, that gap is eight hundred milliseconds of nothing happening. The user, reasonably, concludes the tap missed.
So they tap again. And the order, or the message, or the payment, exists twice — because a state change that would have taken one line was never needed in the environment where it was written.
Free Interaction Review
See What Your Product Does After a Click
Give us access to your product. We will use it on a throttled connection and tell you where actions go unacknowledged.
Claim Your Free Marketing Audit
Enhance Your Brand Potential At No Cost!
- Expect a response within 24 hours
- NDA available upon request
- Dedicated product specialists