Google just reintroduced physical navigation buttons to Googlebooks — the little onscreen controls that let you move between screens without swiping.
In 2011, Google made a decision that seemed purely technical. They stripped physical buttons from Android hardware and moved navigation into software, including gesture controls and onscreen buttons that could disappear or rearrange. The business case was clean — you eliminated hardware cost, maximized screen real estate, and manufacturing got simpler.
What actually happened was a shift in whose bodies mattered. Physical buttons work when your fingers are cold, when your hands shake, when your eyesight isn't sharp enough to locate a centimeter-wide target in bright sun, but software buttons work beautifully for people with steady hands, normal vision. The fine motor control that swipe-and-tap requires.
Google didn't set out to disadvantage older readers or people with tremors. They optimized for the user who could afford the newest phone and had the reflexes to match the design. Everyone else adapted or fell away. Now Googlebooks is bringing the buttons back, not because Google suddenly developed a conscience about accessibility. Because reading on a Chromebook is functionally different from checking Instagram on a phone. An older reader with a book might not touch the screen for hours and doesn't need precision or rehearsal to find a physical button.
Google didn't set out to disadvantage older readers or people with tremors.
What's revealing is that Google built an entire navigation paradigm around what gesture controls could do, then discovered the paradigm didn't actually work for the thing it was trying to optimize. They'd solved for speed and efficiency, which is different from solving for use. Watch what else gets buttons pushed back into the software you use daily. Every return of a physical control is a confession that the previous design worked better for someone you weren't thinking about when you simplified it.