This IEEE Spectrum feature interviews button expert Rachel Plotnick on the resurgence of tactile controls in consumer technology, examining why physical interfaces are returning after a decade of touchscreen dominance. The article strongly advocates for human-centered, inclusive design that considers multiple user populations—particularly blind and disabled users, gamers, musicians, and drivers—while emphasizing the importance of learning from technological history. The editorial engages substantively with accessibility rights, safety concerns, worker collaboration, and cultural/scientific participation; however, the site's significant membership paywall creates a structural contradiction by gatekeeping content about accessibility itself.
> home appliances like stoves and washing machines are returning to knobs
It can't come a bit too soon. My oven has buttons that aren't actually raised from their surroundings, and presses are registered via some sort of presumably fancy processing that I guess sounded slick when it was being pitched, but in practice means that it's very, very difficult to be confident that a button press will do anything, especially when fingers are greasy from cooking.
Oh, and sometimes whatever processor it's using gets frozen up, so I have to turn it off and back on again. But, since it's hardwired, this involves toggling a fuse. I'm sure that there are many ways that this is a better oven than the one in the many-decades-old apartment where I used to live, but I never had to re-boot that oven.
One thing that would really get me to consider buying a Tesla is to add a few high quality _assignable_ knobs and controls that I could configure to control radio volume, heat, or whatever function I'd like. (within reason)
Oh and real indicator stalks, that would be nice too.
As a synthesizer enthusiast, I'm excited to read about this. A well-designed button layout on a synth sparks my creativity. Tweaking knobs on a touchscreen doesn’t work for me because I constantly have to check the screen to make sure my fingers are on the right control.
The worst of both worlds is Touch Buttons. No screen, just a touch-sensitive surface that's divided into areas that activate upon any kind of skin contact, whether intentional or not.
I always see my dishwasher having some bizarre setting active because of accidental contact with a touch button.
Interestingly, almost all designers know that touch screens in cars are bad idea. They always knew it. Bit for some reason, the designers in automotive industry were the only ones who didn’t know. It’s a mystery.
Yes I do prefer analog controls. Dials for heat. Open close flaps for vents. On off switches.
Tangentially: the Tesla single giant glass console is in dire need of a UX designer to take the clutter out and make it far more usable. It’s here I wish that Apple had bought Tesla many many years ago: CarPlay as they have it now where it takes over the whole screen would have been amazing.
Just in time. Yesterday I had to use a touchscreen-based card reader for the first time to pay for something. What a jarring interaction. Impossible to use muscle memory, so I actually had to think what my PIN was and had to look at the screen the whole time, being stressed about pressing just a bit too much to the left or the right so that the wrong digit would be entered. I very much prefer classic card terminals, thank you very much.
I'll be the contrarian and say I prefer touchscreens. To get some system into a touchscreen you need to digitize the whole system which allows you to control it through automation which creates a more versatile system. The system could be digitized and then have a physical control to change the state, but then it's not necessary at that point.
Lack of tactile feedback for the sight-impaired is the obvious part but there is another thing:
Touchscreens just stop registering your touch when you get old. The older you get the less moisture there's in your skin, which at some point makes touch screens ignore you.
Let it be known that (good) designers are fully aware of how bad touchscreens are, with regards to UX and many other things.
It's just that touchscreens have been the least bad option, when you really need/want (always arguable, of course) to iterate a lot on the software, that is inside an expensive and not cheaply/easily modifiable piece of hardware.
Touchscreens in cars should have been illegal to begin with it. How can it be that operating a cellphone is not allowed but operating a “tablet” is a necessity?
Once upon a time I used Android Auto and things were good. Most controls were in the corners, you see, which allowed me to perform a couple of changes without looking at the touchscreen.
One day, a GUI designer decided to put a horizontal bar going through the top of the display just to display a very tiny clock on the top right corner.
The top left corner I used to bring up the menu and quickly select options no longer worked reliably as it was under that horizontal strip.
I stopped using Android Auto after a couple of months.
Touchscreens are perfectly fine on phones, tablets etc. But for something like a car it takes a special kind of idiot to implement a touch only way of controlling things like heating/ac, volume, etc.
Even for certain audio controls it makes no sense. My (fairly old now) Toyota's touch screen is needed for switch between radio and usb (no carplay/android auto), even thats annoying to use.
Finally, also note that an LCD screen is not needed at all in the driver's console. Analog indicators for speed, rpms and simple lights are just fine. What I would really really like to have on all vehicles is an error LCD screen that describes with full and clear details any type of malfunction. We're still stuck with error codes but hey we give owners all these fancy and unnecessary digital toys and when a problem araises we need to plug a scanner to decode what's going on with our vehicles.
The Sony WH-1000XM5 (newest version) headphones have both touch and voice controls, but they can be frustrating to use. The touch controls are meant to be easy, but they’re often too sensitive or don’t respond well. For instance, a small accidental swipe can pause or skip a song, which interrupts my music. The voice feature, "Speak-to-Chat," stops the music if it hears you talking or even singing along, which can be annoying. I usually turn off these controls because they’re more hassle than help—it’s actually easier to adjust the volume on my iPhone when I’m on a run. These controls are 10x worse than the much older versions that had volume and pause buttons on the headphones.
I'm glad the pendulum is swinging back with this one. With UI paradigms, we seem to have this tendency to throw out the baby with the bathwater, or be so intrigued with the possible new benefits we can get (buttons can change according to context!) that we forget what current benefits we would give up to get them (learnability and muscle-memory because the button always does the same thing, being able to feel your way to a button without looking at it)
It reminds me of what happened with the flat UI/anti-skeuomorphism wave a bit over a decade ago. It seemed like someone got so incensed by the faux leather in the iPhone's Find My Friends app (supposedly made to look like it had the same stitching as the leather upholstery in Steve Jobs' private jet) that they went on a crusade against anything "needlessly physical looking" in UI. We got the Metro design language from Microsoft as the fullest expression of it, with Apple somewhat following suit in iOS (but later walking back some things too) and later Google's Material Design walking it back a bit further (drop shadows making a big comeback).
But for a while there, it was genuinely hard to tell which bit of text was a label and which was a button, because it was all just bits of black or monocolor text floating on a flat white background. It's like whoever came up with the flat UI fad didn't realize how much hierarchy and structure was being conveyed by the lines, shadows and gradients that had suddenly gone out of vogue. All of a sudden we needed a ton of whitespace between elements to understand which worked together and which were unrelated. Which is ironic, because the whole thing started as a crusade against designers putting their own desire for artistic expression above their users' needs by wasting UI space on showing off their artistic skill with useless ornaments, but it led to designers putting their own philosophical purity above their users' needs, by wasting UI space on unnecessary whitespace and forcing low information density on everyone.
I am really hoping this and similar projects take off and find mass success -- and tactile controls become more widely deployed across all devices for human-input.
I specifically bought a Mazda because it's the only car that feels safe to actually use. HVAC, audio, maps, calling, absolutely everything can be done with physical controls that minimize eyes-off-road time. There's no situation where you're sticking your arm out trying to tap some tiny on-screen button to get directions. Taking rides with other people in Teslas, subarus, fords, etc, is just wild. Having to go into a menu to change from vents to defrost is crazy, I don't understand how that's even legal.
It seems like total lunacy to me that car manufacturers are putting essential functions (like controlling the HVAC) behind a touch screen.
With my old car, I could keep CarPay navigation on the large touchscreen while I could simultaneously turn on the seat heater and adjust the temperature by blindly hitting the physical controls. In my new car, I literally have to press the screen to bring up the HVAC UI which then overrides CarPlay (and thus hides my navigation). This is completely insane to me.
> presumably fancy processing that I guess sounded slick
I'm pretty sure that capacitive touch sensing is just cheaper than physical interfaces, it's more to do with corner cutting than being slick. All you need to create a capsense "button" is some traces on a PCB, they're essentially free if you're making a PCB anyway.
Enhance Auto has intriguing products that may be right up your alley[0]. That being said, they're obviously aftermarket and not OEM. Last I heard they were working on aftermarket stalks, but I'm not sure where they're at on that project.
Don't forget to pair the Touch Button with a Minimalist design that gives no indication if a button has been pressed!
Bonus points for a big long click buffer and strange multi-click semantics so that once the computer unfreezes your attempts at diagnostics are redirected into messing up the state in weird and wonderful ways that you will have to unpack over the next week.
Cost. They put them in to save money. It’s not a mystery at all. Plumbing wires for a bunch of analog switches is more expensive than one databus, and then there is the simplicity of turning your hardware problem into a software one.
A tiny amount of water getting on these buttons can make them go nuts too… I absolutely hate the electric stove ranges with surface touch buttons… as if those never get water on them…
A poorly designed synth doesn't generally cause a car accident though, far less of a legislative impetus to stop softwaring everything in synth-land =)
I've been relatively convinced that it was a cost savings measure. Both in cost of components and, probably more importantly, cost in labor of install, since touchscreens are cheaper on both regards. Everyone knew it was worse, but it saved money, and, at least for a while, it could be marketed as "premium".
The designers are not the ones who decided on that. It’s cost reduction, feature flexibility (you can decide later what exactly to provide in the software), and the marketing semblance of a cool modern interface.
the obvious consequence of electric vehicles is live configurable filters and patches for performance tuning. I want an ADSR for my accelerator in different modes. give me an EQ for acceleration and braking, along with a feedback cycle for cruising, and the era of performance personalization will be huge.
I would buy a tesla instantly if you gave me a eurorack dashboard insert!
eurorack module designers have moved hardware interface design to where they can create intuitive design languages as well.
I love how my stove’s capacitive buttons sometimes don’t register when I’m using one hand to stir with a conductive spatula while trying to turn down the temp with the other until I let go of the spatula.
The worst variation I’ve ever seen, courtesy of r/CrappyDesign: My oven uses a touchscreen, so whenever I open it, steam gets on the touchscreen and messes with the settings.
There's a interesting middle ground, programmable button that is also a rotary button that gives feedback, the KeWheel by KEBA. I'm sure that are similar solutions from other manufacturers.
You probably meant other industry but this is a terrible mindset for cars for example. Touchscreens are so terrible premium manufacturers ignored them for a long time since its obvious downgrade in comfort and safety, yet people kept buying teslas despite this, even bragging how cool some cheap ipad is.
I spent (5y ago) so much time searching for induction stove with physical knobs. The touch interface at my previous place was driving me crazy, a slight misalidgment and the stove would beep like it’s end of the world. Luckily Miele produces some at the premium price (or was at the time) but I considered it an investment in my mental health.
At a former company, we were all issued YubiKey Nanos, which just never worked for me. None of my coworkers had a problem, but I couldn’t get the damn thing to register a touch no matter what I did, including swapping keys.
Eventually I came across a thread on an internal list for employees over forty, with several other people who were all having the same problem. The solution? Lick your finger. Gross, but it did the trick. And I’m stuck licking my finger every time I need to make a YubiKey work.
> She started getting frustrated, “it’s my fault, I don’t know how to use this thing properly.”
This is heartbreaking. The woman is being excluded through no fault of her own, and she blames herself. I find this to be a common for people who don’t think of themselves as disabled but are made disabled by bad interfaces. They think there must be something wrong with themselves because everyone else has such an easy time, when really it’s the technology.
Dishwasher, same thing. Half the time it won't register a press when I need it to turn on. Yet the cat can start a cycle when he decides he wants to have a climb.
> Yes I do prefer analog controls. Dials for heat. Open close flaps for vents. On off switches.
Dials and switches can be fully digital (e.g., dials can be free-spinning, without locks at each end of a setting). So preferring dials and switches seems reasonable. But flaps for vents are very difficult to automate. Returning to manual flaps in cars would mean losing modern cars' ability to associate and restore HVAC vent preferences with driver profiles. It would mean returning to the time when it was actually necessary to adjust the HVAC vents every time you swapped drivers. While setting vent preferences on the screen may take a second or two longer than manually setting them, thanks to the setting being associated with my driver profile, it's a set-once-and-forget-forever setting. The net time and annoyance savings is large.
Its so great when you know where the buttons are located, that you can touch them in the darkness without them suddenly selecting anything. When you need to make sure "is this the second one from the left?", then apply some force to actually change its value.
Have seen laborers and blue collar workers, my father included, that have to use their knuckles because their finger tips are too callused and dry for touchsceens. Seems like many groups have these kind of issues.
I'm not playing Call of Duty mobile or watching YouTube on the screen on my head unit. I'm not scrolling TikTik or having a text message conversation on a head unit screen. If you think it's the same thing, you haven't actually driven a car with a screen before.
I'm pretty pro touchscreen to a point. Any driving critical control should be physical. Lights, turn signals, horn, steering wheel controls, etc. Physical controls with physical feedback. Everything the driver should mess with should be either on the wheel or immediately around it and should be physical.
Other than that, I really don't care. When I'm punching in the address on the navigation system, give me a massive screen. When I'm stopped and trying to look up something in my media collection, give me a massive touchscreen. When I'm trying to quickly glance at the map, make it a giant screen so I can see it all quickly. Or better yet a HUD or have it on the instrument cluster.
Did it display an ad before displaying the keyboard? Because I encountered terminals which have physical keyboard but also display an ad on the screen. No physical keyboard? A perfect captive audience.
This was one of the first lessons I learned about good UX design and was the canonical example when discussing what Mac OS classic did right and Windows did wrong.
I think it was Norman Nielson thing or one of those old school gurus.
How are people allowed to work on UIs without learning the core syllabus? The basics of their trade? I grew up on this stuff and I'm not even a UX specialist or a UI designer.
Or are they getting overridden by bad product managers and other shitty stakeholders?
Similarly, I find mixing on a tablet slower than mixing on a console with tactile controls - because you can do things like change multiple things by different degrees at once (you don't have to look at both controls to ensure your fingers are tracking) and adjust a control while looking at the stafe.
In addition to what others are saying, US law requires new cars to have back up cameras and the related screen. So everything else immediately becomes "so we add it to the screen we already have to have, or add a new physical control?"
On another note, I do like my (getting older) Mazda's screen. It has touch, but I honestly forget it does because the control knob is so much better for use while driving. Nice and tactile. Additionally all of the important controls have physical buttons. Only major problem I have with it is that if it can't connect to Bluetooth (which is stupidly often), it decides to switch back to radio, blasting that at me. Then I have to sit there going through multiple menus to get Bluetooth reconnected.
Explicitly acknowledges blind community's struggle for equality: 'The blind community had to fight for years to make touchscreens more accessible.' Recognition of marginalized group's successful advocacy for design equity
FW Ratio: 50%
Observable Facts
Direct quote: 'The blind community had to fight for years to make touchscreens more accessible'
Plotnick identified as 'the leading expert on buttons and how people interact with them'
Article published in March 2025 IEEE Spectrum, peer-reviewed technical publication
Inferences
The quote recognizes historical inequality in technology access and a marginalized group's successful collective action
Positioning accessibility as professional expertise area implies legitimate engineering priority
Publication by established technical organization signals institutional recognition of accessibility as design requirement
Accessibility-as-non-discrimination is central: 'A touchscreen prioritizes the visual.' Explicitly frames touchscreen-only design as discriminatory against non-visual interaction, and advocates for voice/tactile alternatives
FW Ratio: 50%
Observable Facts
Plotnick states: 'a touchscreen prioritizes the visual,' and discusses voice-activated systems (Alexa, Siri) as accessibility response
Article discusses accessibility as design priority alongside other concerns
Content explicitly advocates for multi-modal interface options to address discrimination
Inferences
Identifying visual-only design as inherently discriminatory reflects understanding of accessibility as non-discrimination issue
Advocating for multi-modal interfaces implies belief that equal access requires design diversity
Recognition of blind community's advocacy implies rights-based framing of accessibility
Cultural/scientific participation is central theme: celebrates 'richness of tactile experience,' discusses communities of practice (DJs, musicians, gamers, engineers). Technology as cultural domain and scientific subject
FW Ratio: 50%
Observable Facts
Extended discussion of communities engaging with technology: 'DJs and digital musicians, they have endless amounts of buttons...to make music'
Frames interface design as both technical and cultural: 'these are design questions, but they're also social and cultural questions'
Expert's work treats 'how people interact with' technology as subject of scientific study
Celebrates 'richness of the tactile experience' as valid cultural and experiential value
Inferences
Recognizing multiple communities' engagement with technology reflects understanding of technology as cultural practice
Treating button design as worthy of expert scholarship implies technology is part of scientific/cultural life
Interdisciplinary approach (humanities + engineering) reflects commitment to holistic understanding of technology in society
IEEE's role in publishing and facilitating this work supports right to participate in scientific/cultural life
Safety as human right foregrounded: 'When I'm driving, it's actually unsafe for my car to be operated in that way.' Direct connection between interface design and bodily security/safety
FW Ratio: 50%
Observable Facts
Direct quote: 'When I'm driving, it's actually unsafe for my car to be operated in that way'
Multiple automotive examples: touchscreen replacement by 'buttons and dials to dashboards'
Expert contextualizes: 'simplicity of limiting our field of choices offers more safety in certain situations'
Inferences
Identifying unsafe interface design reflects concern for right to life and bodily security
Advocating for design change based on safety concerns implies recognition that technology affects human safety
Automakers' adoption of buttons per safety concern validates that design choices affect security rights
Autonomy and freedom from arbitrary interference explicitly foregrounded: 'fears and fantasies around pushing buttons were the same 100 years ago...about control and who gets to push the button'
FW Ratio: 50%
Observable Facts
Expert states: 'persistent anxieties over time about control and who gets to push the button'
Connects button-pushing to power and agency across 100+ years of technological history
Discusses difference between passive observation and active control: 'you don't always have to look at them—you can feel your way around'
Inferences
Identifying 'who gets to push the button' as perennial concern reflects awareness of autonomy as power issue
Framing tactile control as liberating (feeling without looking) implies recognition of autonomy as fundamental right
100-year historical perspective suggests autonomy concerns are intrinsic to technology interface rights
Multiple communities explicitly recognized and their agency validated: 'the blind community had to fight,' gamers, DJs, musicians. Recognition of organized groups with distinct needs and collective voice
FW Ratio: 57%
Observable Facts
Blind community identified as group that 'had to fight for years' — recognizing collective action
Gamers identified as community with valid preferences: 'they want to push a lot of buttons'
DJs and 'digital musicians' explicitly discussed as communities with interface expertise
Expert describes communities as having distinct 'hunger' for different interfaces
Inferences
Recognition of blind community's collective action reflects awareness of organized marginalized groups
Discussing multiple communities' preferences implies respect for assembly and association
Framing communities as having valid expertise respects collective human agency and rights
Design equity as requirement: 'Having multiple interface options is the best way to move forward.' Advocates that equal protection requires inclusive interface design for different populations
FW Ratio: 50%
Observable Facts
Direct statement: 'having multiple interface options is the best way to move forward'
Article discusses specific populations with different needs: blind users, gamers, musicians, drivers
Expert calls for 'carefully considering what the right interface is for each situation'
Inferences
Advocacy for multi-option design reflects belief in equal protection through inclusive design
Situational design consideration implies recognition that groups have different legitimate interface needs
Emphasis on historical lessons suggests equal protection analysis informed by experience
Worker knowledge and collaboration emphasized: expert describes conversations with companies about safety-critical devices (medical). Calls for humanists to collaborate with engineers
FW Ratio: 57%
Observable Facts
Expert describes working with companies on interface design for medical devices
States: 'these are design questions, but they're also social and cultural questions'
Advocates: 'people who are in the humanities studying these things...can also speak to engineers'
Discusses improving medical device safety to help people feel confident using life-saving equipment
Inferences
Consulting expert knowledge reflects recognition of worker expertise as valuable and necessary
Framing design as interdisciplinary implies workers across disciplines have valid contributions
Focus on medical device user experience implies concern for conditions of work and safety
Educational content about technology history and design philosophy: 'I wanted to understand an origin story...where buttons came from.' Emphasizes historical learning for present design decisions
FW Ratio: 50%
Observable Facts
Expert describes research goal: 'I wanted to understand an origin story...where buttons came from'
Emphasizes learning from history: 'we can learn what mistakes not to make and what worked well in the past'
Advocates for long-term perspective in engineering: 'sometimes things were simpler or better in a past moment'
Inferences
Commitment to understanding technological history reflects educational and scientific engagement
Framing history as instructive for present design implies education as key to better technology
Structural gatekeeping contradicts educational value and accessibility being discussed
Social order and inclusive design: 'carefully considering what the right interface is for each situation.' Calls for design reflecting multiple perspectives in social/international order of technology
FW Ratio: 50%
Observable Facts
Expert calls for 'carefully considering what the right interface is for each situation'
States companies need to understand 'the history of how we used to do things...and what the future looks like'
Describes design as inherently involving 'social and cultural questions'
Inferences
Advocacy for contextual design reflects commitment to social order responsive to diverse needs
Calling for historical and future perspectives implies long-term thinking about social impact
IEEE's standards role supports establishment of inclusive design norms in professional practice
Duty to community explicitly emphasized: expert describes responsibility to understand user needs ('what would make someone use a defibrillator'), engage with communities. Design as ethical responsibility
FW Ratio: 50%
Observable Facts
Expert describes working with companies to understand 'what would it take to get them to feel okay about' using life-saving safety devices
States design involves 'social and cultural questions' alongside technical ones
Advocates for including humanities perspectives in engineering to better serve communities
Inferences
Framing design decisions as affecting people's willingness to engage with life-saving technology implies responsibility to community
Consulting with users and communities reflects recognition of duty to serve diverse populations
Interdisciplinary approach implies recognition that meeting community needs requires multiple forms of expertise
Preamble principles (dignity, equal rights, human agency) are implicitly engaged through discussion of design affecting human control and autonomy. 'Who gets to push the button' frames power and agency as central concerns.
FW Ratio: 50%
Observable Facts
The article discusses 'control and who gets to push the button' as a fundamental question of power
Expert emphasizes that design affects 'our relationships with each other and the world'
Inferences
Discussion of power and control in interface design implies recognition of human agency and dignity
Framing design as affecting relationships suggests awareness of technology's social dimensions tied to human rights
Rest and leisure as human concern: 'Maybe screen fatigue. We spend all our days and nights on these devices...there's something tiring about that.' Recognition of need for respite from technology
FW Ratio: 50%
Observable Facts
Direct quote: 'We spend all our days and nights on these devices, scrolling or constantly flipping through pages and videos, and there's something tiring about that'
Expert describes buttons as potentially 'de-technologize our everyday existence, to a certain extent'
Frames tactile controls as offering relief from visual engagement and mental fatigue
Inferences
Identifying screen fatigue as design concern reflects awareness of right to rest and leisure
Advocating for less cognitively demanding interfaces implies recognition that constant engagement affects wellbeing
'De-technologization' framing suggests desire to reclaim non-work time from technology demands
Remedy through improved design: companies seeking to address past accessibility failures. 'Companies reaching out to her to learn from your expertise' and improve interface design for medical devices
FW Ratio: 50%
Observable Facts
Companies 'have reached out' to expert to improve interface design
Example: designer discussions on 'medical devices like CT machines and X-ray machines, trying to imagine the easiest way to push a button'
Expert discusses 'what would it take to get them to feel okay about' using safety devices (defibrillators)
Inferences
Industry adopting improved design practices reflects recognition of past accessibility failures
Focus on medical device interface design implies concern for remedy through better engineering
Discussion of psychological barriers to device use reflects comprehensive approach to accessibility remedy
Content itself is free expression; advocates for open cross-disciplinary discourse. 'People who are in the humanities studying these things from a long-term perspective can also speak to engineers'
FW Ratio: 50%
Observable Facts
Article is published feature journalism on design philosophy and history
Expert advocates: 'people who are in the humanities studying these things from a long-term perspective can also speak to engineers'
Comments section shows public reader discussion and engagement
Inferences
Advocacy for cross-disciplinary dialogue implies commitment to free intellectual exchange
Publishing expert's perspective reflects editorial commitment to diverse viewpoints
Gating free expression content contradicts spirit of open discourse being advocated
Recognition of user agency: expert frames people's interaction with technology as active and valid. 'There seems to be this kind of richness of the tactile experience that's afforded by pushing buttons'
FW Ratio: 60%
Observable Facts
Expert acknowledges: 'people seem to have a hunger for physical buttons'
Article recognizes gamers and musicians as active communities with distinct, valid interface preferences
Describes users exercising choice: 'DJs and digital musicians, they have endless amounts of buttons...to make music'
Inferences
Framing user preferences as valid ('hunger,' 'richness') implies recognition of persons as agents with legitimate needs
Discussing different communities' interface choices reflects acknowledgment of personhood and agency
Implicit political participation: design as decision-making affecting populations. Call for inclusive participation in design decisions affecting multiple groups
FW Ratio: 60%
Observable Facts
Expert advocates: 'carefully considering what the right interface is for each situation'
Describes companies 'reaching out' to engage expert perspective
Calls for including 'people who are in the humanities' in engineering decisions
Inferences
Argument for inclusive design decision-making implies belief in democratic participation in technology governance
Emphasis on historical lessons for present decisions reflects political engagement with technology futures
Household technology discussed: 'stoves and washing machines are returning to knobs.' Recognition that design affects daily living standards and household adequacy
FW Ratio: 40%
Observable Facts
Article cites 'home appliances like stoves and washing machines are returning to knobs'
Discusses design choices affecting usability of everyday household technology
Inferences
Focusing on everyday appliances implies recognition that mundane technology affects living standards
Interest in button/knob design reflects concern for usability in daily household life
Household technology implicitly framed as important to adequate living conditions
Implicit privacy concern: tactile interface preference implies desire for interaction not dependent on visible observation. 'You don't always have to look at them'
FW Ratio: 50%
Observable Facts
Article discusses visual vs. tactile modalities: 'you don't always have to look at them'
Implicit contrast between observable screen interaction and tactile feedback that doesn't require visible engagement
Inferences
Preference for hidden, non-observable interaction may reflect subtle privacy interest
Contrast between visible screens and tactile controls implies some awareness of observation as design concern
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 11:31:12 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.