Currently Internet witnesses increased complexity around content management systems, accessibility, rich internet applications (RIAs), mobile, application frameworks, syndication, and other multiuse channels, each of which may require to display the presentation of financial information – or a lack of any presentation information – associated with it. In the face of this requirement, most off-the-shelf software packages are damaged by terrible UI practices, not to mention financial and money management software created individually by developers who don’t know any better. Starting with substandard WYSIWYG (what you see is what you get) editors in many popular content management system (often used to display financial data about loans or currency values) to server-side frameworks that create code for users, the UI problems are present in all places.
The good news is that a great deal of current UI issues are almost as fixable as they are pervasive. Although the majority of people involved in the industry believe them to be inherent to Web development, the reality is that they are stubborn relics of bad practices from the 1990s that have persisted into this decade.
A simple approach is to differentiate between short-term and long-term liquidity constraints and the reasons leading to the constraints. If deteriorating fundamentals are the driving force, an indepth credit analysis should specify the point in time when a company will run out of cash. The thing an investor has to decide is whether current trading levels compensate sufficiently for the uncertainty of improving fundamentals and hence the ability to preserve enough liquidity in the long term.