I'm exploring the benefits of using Mozilla Prism (Site-Specific-Browsers), for one of our enterprise level products.
It makes a lot of sense to the web-development team, - they get to focus only on one browser (layout engine); - the time to develop-test-rollout new features is drastically cut down; - and training is a easier to the "non-web-savvy" users.
But there are also some serious disadvantages that we foresee, such as - user would be tied to a custom client (customized Mozilla Prism in my case). - secondly those users trying to access the applications from random computers would always need to get the client, which might become annoying.
I'm open to all of your thoughts and experiences if any in using Site-Specific-Browsers (SSBs) or Mozilla Prism in particular.