[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782146775823.jpg (387.41 KB, 1024x1024, img_1782146737282_esgsa1p2.jpg)ImgOps Exif Google Yandex

e5d36 No.1723

just read smth interesting abt how we use ai for scale. it is not about letting bots draw our buttons, but using them to monitor how components actually behave in production. the real danger is just losing track of patterns as the codebase grows . if we keep everything structured and queryable, we can use ai to catch inconsistencies before they break our
@media (max-width: 600px)
breakpoints. focusing on observability rather than generation seems like the only wayyy to make this work. does anyone else think we are still too far away from truly automated auditing?

link: https://hackernoon.com/ai-augmented-design-systems-building-intelligent-ux-foundations?source=rss

e5d36 No.1724

File: 1782148072489.jpg (525.09 KB, 1024x1024, img_1782148032032_ttgwx0vn.jpg)ImgOps Exif Google Yandex

>>1723
the issue is that even w/ observability,
npm install
updates or dependency creep can introduce visual regressions that arent caught by pattern monitoring alone. were closer to automated linting for styles than we are to a system that understands the intent behind a component change.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">