There are a variety of differences between application and browser deployments detailed in the table below. However, the major drivers in making a choice are usually based on two things: optimal user experience and cost factors.

In the majority of situations the browser is the most popular deployment option. The browser is seen as the easiest way to maintain information access to a wide variety of users, and it is a well known end user application. These factors can reduce costs in deployment, maintenance and training.

Yet in small, localized deployments, the application choice may still be the most cost effective. This is because in its simplest form it does not require an application server. The application option is also the obvious choice when a browser environment might lend to end users browsing away from critical information, such as in critical 24/7 monitoring solutions.

Pros and Cons

Issue	Application Deployment	Browser Deployment
Setup	Server:  No application server required Client: No browser required on client but more labor intensive deployment for wide geographic areas	Server:  Requires application server  Client: Browser required on client but easy deployment for wide geographic areas
Usability	Users must learn a new application but they cannot browse away from critical information being monitored	Users do not need to learn a new application but they may browse away from critical information
Performance	Load balancing and fault tolerance must be implemented	Load balancing and fault tolerance are included with application server
Security	Most applications run on LAN so no security issues	Security issues must be considered
Scalability	Fully scalable	Fully scalable
Server Management	File and version maintenance manually created	Centralized file and version maintenance handled via application server
Cost	Lower for small deployment and higher for large deployment	Lower for large deployment and higher for small deployment

Choose Application Deployment

Choose Browser Deployment