Let’s talk

Back to writing

Component design

What a dropdown needs beyond an options list

A practical checklist for searchable choices, loading states, and dependent fields.

Choose the simplest interaction that fits the list

For a short, familiar list, a native select is often enough. For a city list or a catalogue that changes as someone types, a searchable picker may be worth the extra behavior. I start with how many options a person expects and how easily they can name what they’re looking for.

Plan states before styling the component

I sketch the closed, open, loading, empty, and error states together. An empty search result needs a different message from a failed request. If the selection depends on another field, define when it clears and how the interface explains that change.

Check the keyboard and the saved value

I check that people can reach the control, move through options, commit a selection, and dismiss the popup with the keyboard. Then I test a slower response, a changed parent field, and a failed save. The visible label and the value sent to the server should agree after each one.

Have something in mind?

Let’s talk.

Tell me what you’re building. Let’s find the right way to bring it to life.