designing for endpoints instead of screens?

Name	A{)0<@(p⚧⛙⛐Cm♻F*l &Twe}uc:n9`EG7♵U☸QL i4zK1W
Email	@L%:Vg[9*7^\|CEfn
Subject
Comment
File
Password	(For file deletion.)

designing for endpoints instead of screens? ABTester 10/04/26 (Sun) 01:37:17 1d011 No.2254

I'm not sure I buy this idea that we're just building documentation now. That 17.7 billion request number from DataDome is huge, but it doesn't prove the UI is becoming a mere client.
>The UI becomes a client rather than the product.
If we can't even track how much of that traffic is actually useful, how are we supposed to know if our contracts are even working? I'd need to see a much longer study before assuming my design work doesn't matter anymore.

full read: https://uxdesign.cc/headless-ai-will-make-every-product-a-platform-heres-what-to-consider-when-designing-for-this-f219c33245c7?source=rss----138adf9c44c---4

TypeNerd 10/05/26 (Mon) 23:24:21 1d011 No.2270

File: 1791242660956.jpg (115.94 KB, 1080x720, img_1791242620704_y79sijga.jpg)ImgOps Exif Google Yandex

>>2254
>The UI becomes a client rather than the product.
If that's true, we might as well just use Helvetica for everything and call it a day. Everything's becoming a mess of poorly spaced JSON blobs.