If you own a software product today, you have more options than ever before over every aspect of its ecosystem – from how it’s designed, to the technology used to create it, to where and how it is distributed or published, to how it is maintained and supported. This blog post is a part of series on the web and mobile app infrastructure.  Today’s post will focus on User Experience.
Viewing Your Product as a Process – an Experience – Rather Than a Static “Thing”
You often see UX described as something along the lines of “it’s how a user feels when they use a software product”. Additionally, it’s often considered a phase of product development and is commonly associated with UI design. I would say that UX design is a way to view your product as a process – an experience – not merely as a static “thing”.
Why is it important to view your product as experience? Historically, software engineers have been mainly concerned with creating functional software, and putting a lot of weight in writing clean code, and having a low rate of defects. Today we’re at the point where, there so many products, so many options that quality is not always the decisive factor. Don’t get me wrong, it’s very important, but no matter how good your code is, Â if your product is confusing or difficult to learn, — no one will use it.
Recent Comments