2 ms·
People do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between w
by sneak 4y ago
People do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between writing React components (UI) and designing flows in Figma (UX).
It's just outsiders who say UI/UX as if they are the same thing.
- Retric 4y agoYet I’ve seen people use the opposite definitions professionally. IMO it’s not the kind of thing that’s worth trying to get people to change.
- deleted 4y ago[deleted]
- hot_gril 4y agoI'm a backend SWE. How are those two roles not just UI designers and UI SWEs? Or frontend as our team would say. I get that "experience" suggests something grander than "interface," but that sounds like how I call myself a SWE just to sound better than programmer (which nobody calls themselves anymore, so there's no real difference). Maybe instead of backend we can say "cloud-end" cause "RESTful JSON API" lost its zing.
- deepsun 4y agoIn our company: Writing React components -- frontend engineers (no "UI"). Designing flows -- UX (no separation on UXD/UXE, and they actually have to sit in meetings a lot, to figure out what users want and how others do it). And we use "UI" for folks in design industry: images, colors, fonts, look-and-feel, modern fashion, transition animations, etc. Maybe some nice interactivity that UX didn't care enough for.