ABSTRACT
When software providers create applications and services, often times, there are things that could have been implemented but were left out of the release for one reason or another. Users of such an application or service frequently ask why a feature would be left out. The fact is, there are many reasons that come into play as to why a software company would leave out features, or functions or some component of a software product. Some reasons to limit functionality could include explanations that the provider:
Did not know there would be a want or need for a particular feature, whether it be by the market, or by a particular segment of the market Did not believe that a feature was important enough to delay the release of a product so they could ensure that a particular feature would be 100% tested and complete Did not fully comprehend the capabilities of their software, and that by adding a feature, they could extend the usefulness or management of their product Chose not to provide native integration with other applications or services
Those are all valid points in the business world. Those of you that work for software companies know first hand that getting a product “to market” is sometimes more important than just having the best product. As a result, the end users of these products sometimes have to wait a while before desired features are made available. With any product or set of products, as the technology proliferates and attains different levels of maturity, additional features become available and more capable.
