If only all responsibility for your web applications stopped once the solution is delivered and the client pays up. CrunchyCode helps you deal with typical post productionisation software challenges such as usage monitoring, performance tuning and of course, enhancements.

Almost all * CrunchyCode webpages contain built in timers which count the end to end elapsed time between the moment a user clicks on a hyperlink and the completion of rendering of that webpage, including any javascript as perceived by that end user. This is not a generic server based timing mechanism. These typically don't take into account the network latency and bandwidth or speed of the end users computer (which is important for measuring the impact of DHTML effects such as client side table sorting ).

Web apps built with CrunchyCode actually have usage tracking built directly into the application itself so that you can monitor true "user-perceived" application performance as well as identify the proportion of time spent rendering server side content vs dynamic client side effects. And of course, the plain vanilla count of hits on each specific page (often helpful to determine which screens aren't even being used) is also available.

Even if your apps work well on day one, evolving client needs can render your applications obsolete. CrunchyCode allows you to migrate between user interfaces and middle tiers to suit.