@tomjohndesign Fair, and this is definitely where I still use Figma - but I just prefer it to be ignorant of the data (to some extent). Anyway, always interested to hear more about process from one of the top designers in the game. βοΈ
@tomjohndesign Iβm speaking purely to your point around designing data heavy applications - much easier to work directly with the data in its current form (strings, Booleans, enums etc.) vs. extract it and manage it in an entirely new one (layers, frames, etc.).
@tomjohndesign Interesting, personally Iβve found wrangling 1000s of layers / frames more difficult. Now of course you can invest in components and tokens, but that already exists in code.
@tomjohndesign AI design tools arenβt (yet) capable of production UI/UX, at least not for those with taste. But this is too narrow. If, via AI, the medium shifts from vectors to code, why not design in code? AI is redrawing the boundaries of design and we should take up the mantle of frontend.
@ryolu_@cursor_ai This x1000. Iβve been building / coding my entire βdesign careerβ, itβs just now with tools like @cursor_ai I can go much further, and with the necessary elements that the rest of my (any) engineering team requires (i.e. with testing, performance, security, etc. accounted for).
@kenwheeler Sign. Me. Up.
Just moved here from the UK and for the life of me I canβt find a carpeted pub with a dart board, and some god awful / angel derived lager for Β£2.20.
Bring back βshit, but knows itβ as a vibe.