User talk:Ritikfriend

Evolution Role of Software
Design professionals often decry the lack of importance and investment their companies place on design. After all, most software projects revolve around a product’s engineering, to the ongoing detriment of its design—not to mention the chagrin of so many designers, who wriggle uncomfortably toward the bottom of the food chain. But there is a good reason for this: products can be very profitable without investing a single penny in interface design—at least, beyond the user interfaces the engineers build. Indeed, at least in the early stages of a market or company, resources dedicated to intentional interface design are often a bonus rather than being viewed as a necessity. Sound crazy? Consider the natural and normal evolution of a software product: It starts with an idea.—In the beginning, somebody has an idea. They see a market opportunity, or they see a solution to a problem, or they see something that they find fun or enjoyable. They have vision, they imagine a product or service, and they want to make a commitment to make it real. That is where it begins: in the mind, in the realization that an opportunity possibly exists to create something new and different—or better. Then, the idea must become real.—Having an idea is not enough. For the idea to have value, a company must make it real. If it does not work, there is no product. For a software product, making an idea real requires engineering, and engineering can also produce the product’s user interface. It may not be very usable or attractive, but at least it can work. It is through engineering that the product becomes real. Finally, the real must become ideal.—This is where design often enters the equation today. Once engineering has built a functional product, people realize they need to make it more attractive and/or usable, and formal, professional, intentional user interface design becomes necessary.