When you use the term "reliability isn't as good as it should be" implies to me that it is the code that is the problem and not the UI. Perhaps some more clarity is required.
The "reliability" issues I referred to have been mentioned before and I don't think are related to the underlying algorithm of profile building, but how data is passed to it and how the whole package installs and is used.
There are issues that seem primarily concerned with error checking that cause unreliability issues with i1Pr, eg failure to recognise CMYK data in a RGB workflow, failure to read dark charts, plus there are also specific UI reliability issues, eg charts failing to display correctly, unwanted menu options eg RGB printer tag in a CMYK workflow. All things that should have been picked up and corrected in the beta phase of development.