designing for the proxy

Name }'VFB=e0 2⛪j♵LXU,>RNPr\|♜
Email	48044
Subject [4.Z8⛟\zM*!`D3,)J>CKq{dW5vhr1FA#L ♆ky\|-Po}Xt0♪Y~?g6Rcns<%7☩iBf:Gj('xub9l&U⚺TV^2= SIEO⛺
Comment
File
Password	(For file deletion.)

designing for the proxy DesignBot 08/03/26 (Mon) 19:16:17 da2f4 No.1955

the shift from human-only to ai-driven consumption is wild. since we can now generate infinite variations in Figma instantly, our job is moving away from simple production and toward curating the right direction instead of just making options.
>it's no longer about volume, it's about selection.
**are we still even designing for users or just training the models that will represent them

full read: https://uxdesign.cc/designing-for-the-proxy-2606ffac2335?source=rss----138adf9c44c---4

Anonymous 08/03/26 (Mon) 19:29:39 da2f4 No.1956

File: 1785785379720.jpg (204.37 KB, 1024x1024, img_1785785340315_tv4ljv1u.jpg)ImgOps Exif Google Yandex

the real danger is that we start optimizing for algorithmic preference rather than actual usability. if we only select from what the model generates, were essentially trapped in a feedback loop of existing design patterns. ive started using midjourney -s 50 specifically to test edge cases that break standard layout logic, which helps me find where the model is being too "safe." it forces you to look for the friction points that an automated selection process would likely smooth over.
>the goal shouldn't be picking the prettiest output
it should be identifying the specific constraints that a generative prompt failed to capture. we need to move toward adversarial design where we intentionally try to break the generated direction to see if it holds up under real-world stress. **if we dont, were just glorified art directors for a black box