Tootfinder

the 2010 smartphone was too inefficient with HTML
the 2010 smartphone needed a distinct simplified m-dot web site
the 2010 smartphone needed a proprietary app store to run native software
it was impossible to make efficient HTML web sites that worked in multiple contexts
the 2026 agents are too inefficient with HTML
the 2026 agents say HTML is too complex and burns too many tokens
the 2026 agents *need* markdown
it is impossible to make efficient HTML web …

Client explaining spec: “Clicking the drop-down opens a product grid menu with pop-ups to choose colors.”
Me: “Wut.”
Technical pedantry is important in UI and digital accessibility work. As practitioners we have to translate lingo all the time.
Suggestions…
• Drop-down: https://adrianroselli.…

Stop Using ‘Drop-down’
TL;DR: Stop using the word drop-down. Instead choose a term that accurately describes the control you want. I have worked both with native platform developers and web developers. While control names might differ, if a control was functionally the same then it was not an issue. A TextBox, for example,…

RE: https://hachyderm.io/@thomasfuchs/116074874092696186
I think this cultural shift actually started around 2008–2010, with the advent of crypto and the metastasizing of complex web frameworks that started to replace native apps.

Ah, the joys of having a built-in native JavaScript database¹ that can persist and load typed JavaScript objects² and an interactive JavaScript shell (REPL)³ in Kitten⁴ :)
:kitten:💕
¹ https://kitten.small-web.org/reference/#database
²