Designing Interfaces for Physical Products: Displays, Buttons and Feedback

The interface of a physical product is more than its screen. It includes the buttons and how they feel, status LEDs, sounds, vibration and the way the device behaves when it is busy, offline or in fault. Each element is constrained by hardware cost, power, enclosure and environment, and each depends on firmware for its behaviour. Good device interfaces come from designing these elements as one system, early enough that the hardware can support them.

At a glance

100 ms
A response within about a tenth of a second feels instantaneous to most users.
1 s
Beyond about a second, users need a sign that the device is working.
Not colour
Status shown by colour alone is lost on colour-blind users and in poor light.
Debounce
Firmware filters contact bounce so that one press registers as one press.

The problem

Device interfaces often grow by accident. A status LED gains a fourth blink pattern, a button gains a long press and a double press, and nobody outside the engineering team can tell what the device is doing or how to reset it.

Hardware chosen early limits what the interface can do. A segment display cannot show a helpful error message, a single-colour LED cannot distinguish states clearly, and a touchscreen that fails with gloves is a problem in a workshop or a cold store.

Every press deserves an immediate response, and every state the device can be in deserves a way to show it.

Feedback the user can trust

Acknowledge every input immediately, with a click, a light or a screen change, even if the action itself takes longer. For anything slower than about a second, show progress; for long operations, show what is happening and whether the user can walk away.

Design the unhappy states as carefully as the normal ones: no connection, low battery, fault, firmware updating and factory reset. A user who can see what state the device is in, and what to do next, does not need to call support.

What good looks like

List every state the device can be in and every action the user can take, and decide how each will be shown and performed before choosing display and input hardware.

Prototype the interaction early with real buttons, displays and enclosure samples, and test it with people who did not design it.

Specify feedback timing, LED patterns, sounds and screen content as firmware requirements, so behaviour is consistent and testable.

Display options for devices
DisplayStrengthsLimitations
Indicator LEDsCheapest, lowest power, visible at a distanceFew states; needs a legend or an app
Segment LCDVery low power, readable in sunlightNumbers and fixed icons only
Monochrome OLEDHigh contrast, compact, simple graphicsSmall sizes; can age under static content
Colour TFT LCDRich graphics and touchHigher power, backlight and processing needed
E-paperHolds an image without power, readable in sunlightSlow refresh, little animation
General characteristics. Specific parts vary in brightness, power and lifetime.
Physical buttons and touchscreens
Physical buttonsTouchscreen
Gloves or wet handsReliableDepends on panel and tuning
Use without lookingPossible by feelDifficult
Changes after launchFixed in hardwareChanged in software
Complex settingsAwkwardWell suited
SealingNeeds careful designStraightforward behind glass
Many products combine a few physical controls with a screen.

What it changes

Clarity

Users can tell what the device is doing and what it needs from them.

Fewer Support Calls

Clear fault and recovery states let users solve common problems themselves.

Right Hardware

Displays and controls are chosen to suit the interaction, not fitted around it later.

Consistency

A documented interaction model keeps firmware, app and manual in agreement.

Where to go next

Where a companion app exists, decide which tasks belong on the device and which in the app. Essential functions and safety-related status should still work without the phone.

Consider the environment: sunlight, gloves, noise, vibration and viewing distance all change which display, controls and alerts will work.

Problems this prevents

  • Blink codes nobody can interpret
  • Presses with no visible response
  • Status shown only by colour
  • Displays unreadable in real conditions

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.