It has never been more true that UX is not just the graphical interface, but also everything that underlies it: the services around a product, its security, the performance and resilience of its components, and everything else that impacts the user's ability to achieve their goal
Many designers get stuck on "humans reading off the screen, then selecting things" as a model of human-computer interaction, but it has never been sufficient to describe the diversity of available inputs and outputs. Miss me with "UX/UI" - what about "UX/API"?
For enterprise software, users == developers. They drive large-scale business processes, and need the user experience of using your API (or configuring and uploading the Excel spreadsheet) to be just as good as clicking on screens.
For consumer products, a wealth of input data is available - device location/orientation, browsing history, Facebook surveillance data. The designer must understand these flows to ensure that the user's data is used properly, securely, and transparently.
"Should designers code" is not a sufficient question to ask. Should designers be software *architects*? Should software architects be designers? Is it (or has it ever been) reasonable to suggest that any one person can know ALL the things necessary to design a user experience?
This tweet thread brought to you by an overabundance of office coffee. Office Coffee - it may be lousy but it's free!™
