A dropdown with 180 currencies is not a currency selector. It is a search problem disguised as a form field.
Smart defaults
Detect the user's likely currency from their IP-based geo, not from navigator.language (which reflects OS preference, not location):
const geo = headers['cf-ipcountry'] || 'US'; const DEFAULT_CURRENCY: Record<string, string> = { US: 'USD', GB: 'GBP', ES: 'EUR', MX: 'MXN', BR: 'BRL', IN: 'INR', AU: 'AUD', JP: 'JPY', }; const suggested = DEFAULT_CURRENCY[geo] || 'USD'; Show the suggested currency pre-selected with a "change" link that opens the full list.
Searchable, not scrollable
When the full list opens, it should be a text input that filters as you type — matching both the code (EUR) and the name (Euro, евро):
function matchCurrency(query, currencies) { const q = query.toLowerCase(); return currencies.filter(c => c.code.toLowerCase().includes(q) || c.name.toLowerCase().includes(q) || (c.localName || '').toLowerCase().includes(q) ); } Displaying amounts
Always format with Intl.NumberFormat for the selected locale, not by hardcoding $ or € symbols. A site like Oro7 that serves a Spanish-speaking audience needs es-MX formatting where the currency symbol follows the number, not precedes it.
Edge case: multi-currency accounts
Some platforms let users hold balances in several currencies. Display the active balance prominently and others in a collapsible section. Never auto-convert without confirmation — users are sensitive to exchange rates and want to see the rate before it applies.
Takeaway
Respect the user's location, let them search instead of scroll, and format amounts for their locale. Three rules, zero frustration.
