Catalyst's biggest advantage is the same as Perl's: stability. Catalyst is a mature package, with an ecosystem of hundreds of equally mature modules that can cut down development time substantially. These packages allowed us to quickly integrate new database types, and to interface with modern APIs without writing thousands of lines of code.
When an error occurs while working with Cataylst, the problem is most probably with our own code, rather than the platform.
Age is what makes Catalyst so mature and stable, but it is also what makes it hard to find up to date resources and new hires able to write in it. With very few new people being added to the ranks of Perl developers, the scarcity of coders will become a larger issue with time. Eventually the cost of hiring a team will be prohibitively expensive, and lead to us migrating to a newer platform to save on costs.
Consider the cost of hiring experienced developers capable of writing Perl, or the costs of training for new team members.
Stability is the number one problem Cataylst solves; other than that, most other MVC frameworks have similar capabilities.
I really enjoyed how we were visually able to see how far away we, as therapists, were from obtaining a sufficient amount of data for the current session
The interface was a little clunky and not very appealing. It was also very difficult to get technical support in a timely manner. Some issues that needed to be addressed right away were not dealt with until maybe a week after submitting a request
Similar to CentralReach, catalyst has helped greatly with data acquisition. It helps me manage my time better
Easy to track expenses, take photos of receipts on the fly, keep track of submitted expense reports.
There isn't anything that I can think of that I don't like about this tool.
Makes expenses easy for employees and employers too!