Tithi MondalBlog

Article6 min readUpdated

Button States: Design Disabled, Loading and Error Feedback

Button states explained: default, pressed, loading, disabled and error, plus toast messages and success feedback, with do and do-not examples.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Button States: Design Disabled, Loading and Error Feedback: cover illustration

A user taps "Pay now" on a slow network. The button does not change. He taps again, and again. The app sends three payment requests. His bank sends three SMS alerts, and he calls the shop owner in a panic.

The design fault is small. The button had only one state. Good button states prevent this kind of trouble. A button state is the way a button looks and behaves at one moment, for example waiting, pressed or busy.

What button states does every app need?

Every app needs at least five states: default, pressed, loading, disabled and focused. Many also need success and error. Each state should look different from the others, so the user always knows what is possible.

StateWhat the user seesWhat it tells them
DefaultNormal colour and labelYou can tap this
PressedDarker or slightly smallerThe app received your tap
FocusedA clear outline around the buttonThis is the selected control, for keyboard and switch users
LoadingA spinner and a changed labelPlease wait, work is in progress
DisabledMuted colourNot available right now
SuccessA tick or a changed labelThe action worked
ErrorA message near the buttonThe action failed, and here is what to do

Design all of them in Figma as variants of one button component. Developers then build each state from the start, instead of discovering them later. See design system for startups.

How should a pressed state look?

A pressed state should appear instantly and change the button in a clear but small way. Darken the fill, or reduce the size by a few percent. Do it within about 100 milliseconds.

The pressed state is the app's way of saying "I heard you". Without it, people tap again. On a mid-range Android phone with a slow response, this small change is even more important.

Do not make the pressed colour almost identical to the default. Also, do not rely only on a ripple that disappears at once. A hand covers the button when it taps, so the change should still be visible around the edges of the finger.

For button size, placement and wording, read call to action button design and thumb zone design.

How do I design a loading button?

A loading button replaces its label with a short message and a spinner, and stops accepting taps. This prevents double submission, which is the most costly button mistake in payment and booking flows.

Do:

  • Keep the button the same width, so the layout does not jump.
  • Change the label to a present-tense word, such as "Paying" or "Booking".
  • Disable further taps while loading.
  • Add a time limit. If it takes more than about 10 seconds, show a message and a way to try again.

Do not:

  • Show a spinner somewhere else on the screen, away from the button.
  • Let the user leave the screen without a warning during a payment.
  • Keep the old label "Pay now" while the request runs.

For UPI payments, the app often waits for another app to respond. The loading state must say what is happening. See UPI payment UX and checkout design.

Should I use a disabled button?

Use a disabled button carefully, because it often confuses people. A disabled button is a button that looks muted and cannot be tapped. The user sees it and does not know why it will not work.

Take a signup form with a grey "Continue" button. The user filled in everything but still cannot continue, and nothing tells her why. She leaves.

There are two better approaches:

  1. Keep the button active, and explain the error when tapped. If the mobile number is missing, scroll to that field and show "Enter your 10 digit mobile number".
  2. If you must disable it, say why nearby. For example, "Select a delivery slot to continue".

Disabled is the right choice when the action is truly not possible and the reason is obvious, such as a "Next" button on the last page, or "Resend OTP" during a 30 second wait. In that case show the countdown on the button: "Resend OTP in 24 seconds".

Also remember contrast. A disabled button may be exempt from contrast rules, but the label should still be readable. See colour contrast in UI and form design best practices.

How do I show success and error feedback?

Show feedback close to the place of action, in words the user understands, and keep it visible long enough to read. Success can be short. Errors need to stay until the user fixes the problem.

For success:

  • A tick on the button, or a change of label to "Saved", for small actions.
  • A full confirmation screen for important actions like payment or booking, with the amount, the reference number and the next step.

For errors:

  • Say what went wrong and what to do: "Payment failed. Your money was not taken. Try again or choose another UPI app."
  • Place the message next to the button or the field, not at the top of a long page.
  • Keep the button active so the user can try again.

Do not write "Error 502" or "Something went wrong" with no next step. Good error wording is part of UX writing and microcopy for apps, and error screens are covered in empty states, loading and error screens.

When should I use a toast message?

Use a toast message for short, low-risk confirmations that do not need a decision. A toast is a small message that appears briefly, usually at the bottom of the screen, and then disappears.

Good uses:

  • "Added to wishlist" with an "Undo" action.
  • "Link copied".
  • "Message deleted. Undo".

Poor uses:

  • Payment failures. The user may miss them and the money question stays open.
  • Form errors. These belong next to the field.
  • Anything the user must read and act on, such as a change in delivery charge.

Technical points for toast messages:

  1. Keep them on screen for about 4 to 6 seconds, longer if there is an action or a lot of text.
  2. Do not place them over the main button or the bottom navigation.
  3. Make them readable by screen readers, so users of assistive technology hear them. See accessibility in app and web design.
  4. Show one at a time. Stacked toasts are hard to read.

If the message is important, use a banner or a dialog instead. I cover that choice in pop-ups, modals and bottom sheets.

How do I make sure all button states get built?

Include every state in the Figma component and in the handoff document. A button designed in only its default state will be built that way. The missing states then become bugs found by users.

A checklist for each button:

  • Default, pressed, focused, loading, disabled shown in the component.
  • Success and error outcomes designed for the key buttons, such as pay, book and submit.
  • Label text for each state written out.
  • Spacing and size fixed, so the button does not change width.
  • Behaviour on slow networks described.

On fintech and marketplace screens I have designed, the buttons that carry money or a commitment get the most careful state design, because a mistake there costs the user real rupees. For more on that area, see fintech app UI and UX design in India. If you want your app's buttons and feedback designed fully, see UI/UX design or send me a message.

Frequently asked questions

What are the main button states in UI design?

+

The main states are default, pressed, focused, loading, disabled, success and error. Each should look clearly different from the others.

Is a disabled button bad UX?

+

Not always, but it often confuses users because it gives no reason. Prefer an active button that explains the problem when tapped, or add a line that says why it is disabled.

How long should a toast message stay on screen?

+

About 4 to 6 seconds is a common guide, and longer if the message has an action like Undo. Important messages should not be toasts at all.

How do I stop users from tapping a button twice?

+

Switch the button to a loading state as soon as it is tapped and ignore further taps until the response arrives. Change the label so the user knows work is in progress.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.