Enclosure button design: plungers, keypads and feel
Enclosure button design decides how a device feels: switch choice, plungers, silicone keys, tolerance stacks, sealing and tests to run before tooling.

Buttons look like the easiest part of a product, and they are where many small connected devices first feel cheap. A wobbling cap, a mushy click or a switch that dies after a few thousand presses tells a customer more about build quality than any spec sheet. Good enclosure button design is a mechanical problem, an electrical problem and a tolerance problem at once, and it is usually left until the PCB is already frozen.
This post is for founders, product managers and engineers who are about to put one to four physical buttons on a small plastic device. It covers the main construction options, the dimensions that decide how a button feels, and the failure modes we check for on the bench before tooling.
Start with the switch, not the cap
Almost every button on a small device ends in a PCB-mounted switch, and that part sets the limits for everything above it. The common families are:
- Tactile (tact) switches: the familiar 6 × 6 mm, 4.5 × 4.5 mm or 3 × 4 mm parts with a metal dome inside. Travel is short, typically 0.2–0.5 mm, and actuation forces are usually offered from around 1 N up to 3 N or more. Rated life is commonly 100,000 to 1,000,000 cycles depending on the series.
- Side-actuated tact switches: the same mechanism turned 90 degrees, so a button on the edge of the enclosure can press straight down onto a board lying flat. They suit slim devices but put side load on their solder joints.
- Sealed tact switches: versions with an internal membrane rated to IP67 at the switch itself. They protect the contacts, not the enclosure, so you still need to seal the opening.
- Metal domes on PCB pads: bare snap domes held by adhesive film over gold-plated pads. Very thin and cheap at volume, but they need a good pad finish and careful assembly.
Pick the switch force with the whole stack in mind. A plunger or rubber key adds its own resistance, so a 1.6 N switch can feel like 2.5 N at the cap. For a device that lives in a pocket or bag, a heavier switch reduces accidental presses; for a reset button nobody should hit by accident, a recessed, firm switch is better than a soft one.
Four ways to bring the button through the wall
Once the switch is chosen, the question is how the user’s finger reaches it. Each construction has a different cost, feel and sealing story.
| Construction | Feel | Sealing | Tooling cost |
|---|---|---|---|
| Moulded cantilever in the housing wall | Fair, can feel spongy | Poor without extra parts | Lowest (no extra part) |
| Separate hard plastic plunger | Crisp, positive | Needs a gasket or O-ring | One small extra tool |
| Silicone rubber keypad | Soft, well damped | Good, the key is the seal | Compression mould, moderate |
| Membrane or overlay over domes | Short, flat | Good when bonded well | Low tooling, more assembly |
Moulded cantilevers
A button cut into the housing wall as a flexing tongue costs nothing extra in parts, which makes it popular. The catch is material. ABS and PC/ABS are stiff and can crack at the root after repeated flexing, especially with a sharp corner there. Give the root a generous radius, keep the arm long relative to its thickness, and check the strain at full deflection the same way you would for a clip; our notes on snap-fit design for small enclosures apply almost directly.
Separate plungers
A separate plunger in a guide bore gives the most consistent feel, because the plastic only transmits force and the switch provides the click. It is our default on most hard-shell devices. The design work is in the guide: long enough to stop rocking (as a rough rule, guide length at least equal to the plunger diameter) and with a clearance of roughly 0.1–0.2 mm per side, adjusted for the moulder’s capability.
Silicone keypads
Silicone keys are the natural choice when the button also has to seal. Hardness is typically specified somewhere around 40–70 Shore A, and the feel is tuned by the shape of the web around the key and the snap ratio (how sharply force drops at actuation). Ask the supplier for a force–travel curve, not just a nominal force.
Tolerances that decide how the button feels
Most bad buttons we see on audits are not bad designs, they are bad tolerance stacks. The gap between the bottom of the plunger and the top of the switch depends on the PCB thickness tolerance, the switch height tolerance, the standoff or boss height, and the plunger length. Add those up and the gap can easily vary by a few tenths of a millimetre, which is the same order as the switch travel.
Too much gap and the button has dead travel before it clicks. Too little, or interference, and the switch is pre-loaded, feels dead, or triggers by itself when the housing is squeezed. Practical rules we use:
- Aim for a small nominal gap, often in the 0.05–0.2 mm range, and check the worst case at both ends of the stack.
- Reference the plunger from the same part that holds the PCB, so fewer parts sit in the chain.
- Add a hard stop in the housing so a heavy press bottoms out on plastic, not on the switch. Tact switches have a limited overtravel and a maximum static load in their datasheets.
- Support the PCB directly under the switch with a rib or boss, otherwise the board flexes and the press feels spongy.
Sealing and ESD in enclosure button design
Every button is a hole in the enclosure. If the product needs an IP rating, decide early whether the seal is the silicone key itself, an O-ring on a plunger, or a bonded membrane, and design the compression features for it. Then test the buttons fully assembled, in the same leak runs as the housing.
Buttons are also where fingers deliver static. A plastic plunger with a long creepage path to the PCB usually needs nothing more, but metal caps, decorative rings and conductive coatings need a defined discharge path to ground and protection on the switch line. Our post on ESD protection design covers TVS placement and grounding in more detail.
Firmware is part of the button
The mechanical design sets the feel; firmware sets the behaviour. Metal domes bounce for a few milliseconds, and some switches bounce longer as they age, so debounce in firmware with a window long enough for worn parts, not just new ones. Decide long-press and multi-press timings with the industrial designer, write them into the requirements, and keep them consistent across every button and every firmware version.
On battery devices, the button is often a wake source. Use a GPIO that can wake the microcontroller from its deepest useful sleep mode, and check that the pull-up does not quietly draw current when the button is held or stuck.
How we test a button before tooling
We do not trust feel from a CAD model. The checks we run on prototype parts are simple and cheap:
- Force–travel measurement at the cap with a force gauge on a small stand, compared against the switch datasheet curve.
- Cycle testing with a basic actuator rig (a solenoid or servo and a counter) to a target well above expected lifetime use, inspecting cantilever roots and plunger guides along the way.
- Squeeze and drop checks to see whether the housing flexing or a fall triggers the switch.
- Off-axis presses at the edge of the cap to find rocking and sticking.
- Assembly trials with the worst-case parts from the tolerance stack, not just the nicest ones.
What we would do
For a typical small connected device with one to three buttons, we would choose the switch first and read its overtravel and load limits, use separate hard plunger caps for a crisp feel or a silicone keypad when sealing matters more, and run the tolerance stack before the PCB layout is frozen. Then we would add hard stops and board support, agree debounce and press timings in writing, and put prototype buttons through force and cycle tests before anyone pays for a production mould. All of it costs less than the returns a bad button causes.