A good software should be free of errors and very easy to use that everyone will be familiar with it as soon as they start the application. Quality software products and technical support is very influential in software production. The better the support software publishers and shareware authors provide, users are more likely to purchase technical support product.Some is: the product documentation online, e-mail assistance, access to support forums maintained by software publishers, and knowledge base.
Good documentation may exclude in many cases the need for further forms of technical support.
In the software product must have the Read Me file text format that includes: Product Name and Version, Ship date, the Company and author’s name, description (like “photo organizer”), A What’s New list (this should be a list of improvements and new features) , the system requirements (hardware such as CPU, RAM, disk space, supported operating systems), price, payment options and instructions, Copyright and distribution information (rules for people who want to distribute your product), and contact details (email, phone, website fax and postal address). Read Me file is important because everyone who might be interested in your product is expecting it, including reviewers, users, or people who want to put your product on a CD for distribution with magazines or their websites.
Tutorials and solutions. The first thing you should think about when starting to write it is how your users will use it. Few are those who will bother to read them all before trying to use your product. They are more likely to turn to later, when they tried to do something and do not know how to do it, or when they find something they do not understand.Explanations easier to understand if they are supported by drawings and diagrams, wherever possible. There must also be labeled with the chapter “Troubleshooting”, which provides answers to the most common problems. First you have to guess where the problem is probably happening, but some upgrades to your product and then, feedback from people who try the product will tell you what is the most common problems. manual should be divided into several chapters, the first to tell you what other chapters contain, so that people can easily find what they need.
Interface. User friendly is not enough, the interface needs to navigatable even if the user does not have an understanding of the overall system, so that the screen needs to self-describing.
Documentation. Installing documentation website for users to read should appear in search results. This must be arranged so that the user, who must be asking questions like “How do I” or “Why can not I ‘can find instant answers. Many examples showing how to perform various tasks with software products are also needed. A good idea is to include a link to the list of terms that may be more difficult to understand. Attempts to make using your product as a seamless experience as possible, something proper support and documentation can help you achieve.
