WarsawJS #86, Warsaw
Scale is not only autoscaling, load balancing, bundle size, or caching. This talk brings the topic down to a small but stubborn interface element: the picker, or HTML select. From that everyday control, it shows how simple UI choices become product architecture once many teams and users depend on them.
A select can look trivial until it has to support keyboard navigation, screen readers, async data, long option lists, mobile behavior, localization, visual consistency, and performance constraints. The talk uses those pressures to compare native controls with custom components and to show where design-system decisions turn into long-term engineering commitments.
The point is not that every select should be replaced. It is that even familiar controls have hidden costs, and scalable UX/UI comes from knowing which trade-offs belong in the product, which belong in shared abstractions, and which should stay boring because the platform already does the job well.