Despite the design community's tendency to create fad cycles (remember when we spent a year arguing about skeuomorphism?), I'll take this as a positive sign for the maturity of our practice. There are signs that a more conscientious, responsible approach is becoming a stable pillar of our professional identity. However, the challenge of "design ethics" is that once you start thinking about it, you start to notice it everywhere. And it's not just about the business models, it's about the technical and economic structures that enable them. That's an awful lot of context to keep in mind at once.
Ever since I started learning about UI/UX/IxD and all those tech buzzwords, I came across a lot of blogs, articles and pictures that illustrates about the difference between UI Design and UX Design. As a fresh new student in this field, I was initially more passionate about UX Design because it looked as if it was more relative to psychology (which I got a Bachelor's degree in) and less about what was known as GUI (or UI). I thought UI Design would be far, far from me since I didn't learn anything about any of those in college. So, I focused more on learning about UX rather than UI and to be honest, I thought UX was more cooler and important than UI. Moreover, it was common to see people around me, raising up their voices about the importance of UX in every little things and how UI can sometimes be less important.
Years ago, we had doctors - just doctors. They practiced every kind of medicine, had small offices, and even made house calls. We called them general practitioners. As the field of medicine grew and research and knowledge expanded, doctors began to specialize. Now we go to one doctor for ear, nose and throat issues; we go to another for skin issues; we go to others for issues with any of our major internal organs.
How website designers are displaying photographs is changing. They are putting pictures in circles, making them black and white or adding a drop shadow behind them. They want to have visitors drawn to images. Now, they are exploring other ways of showing pictures. Where most websites feature a large primary photo that expands across a site, designers are changing how they present those main pictures.
This book is for the broad community of people who conceive, develop, market, evaluate, and use software. It is foremost, of course, for the software designer, and particularly for the reflective designer---someone who is driven by practical concerns, but who is also able to step back for a moment and reflect on what works, what doesn't work, and why. At the same time, it reveals new directions and new possibilities for programmers who build software, and for product managers who bring software to market. Software users will also find the book valuable in expanding their understanding of what good software design encompasses, which will help them in evaluating, integrating, and productively using computer applications.