“The PCA crew is leagues above
the competition” - Pepsico
"a prior vendor failed to develop
the application, which (Practical) delivered." - Franklin Park
"the application (is) easier to use, with a
much simpler, more intuitive use interface" - Royal Administration Services
"Sometimes it's the things you don't ask for
that are important" - Royal Administration Services
"PCA turned our raw data and algorithms into easy to use
and understand features and reports." - CareScout
"The quality and professionalism ... has been
so outstanding that we want to send you a letter of thanks." - USALCO
"PCA people and applications stand out by
far exceeding our expectations." - USALCO
"The resulting application greatly increas(ed)...
our business effectiveness and efficiency." - The Advest Group
"PCA completes projects
efficiently and effectively" - Pepsico
Browser-Based Applications Pros and Cons
Practical Computer Applications (PCA) has developed many browser-based applications and this is what we have found to be the major pros and cons.
- Runs on any OS. Browser-based applications will run on any computer which has a fully-functional web browser. This may not include many smart devices such as cell phones or PDAs, which use a limited browser which cannot display or interact with non-mobile specific web pages.
- No installation. Browser-based applications do not need to be installed in any way. Users simply navigate their web browser to the correct address. A web browser is required.
- User Interface Differences. Since users may have different machines, different operating systems, and different browsers (with different versions), the display and layout of web pages (and the overall user experience) can change drastically among users. For example, buttons can shift, text boxes can change in size and location, elements can be hidden off-screen or disappear entirely, and images can load incorrectly on overlap other controls.
- Slower Development. Designing and creating web pages is more time consuming based on the HTML and CSS-based architecture of the web than that of .NET Windows Forms. Cross-browser layout issues not only result in delays but also require defensive programming which consumes additional time. Making small layout changes can also require complicated CSS programming (once again accounting for cross-browser display bugs, such as the well-known issues between IE and FireFox), and result in slower turnaround to clients.
- Costly to Development. Slower development and the more complicated programming required to account for machine, operating system, and browser differences among users, creating pure web-based applications is not as cost effective as Smart Client applications.
- Difficult to Debug. Since users of applications can have almost any type of computer, smart device, operating system, and web browser, it can be extremely difficult to reproduce problems reported by users, and therefore even more difficult to remedy problems. A team might require an extensive set of computers of different types, running different operating systems, and with different settings to properly reproduce reported problems, which is often not feasible. The introduction of browsers on PDAs and cell phones makes this even more challenging.
Most Popular Pages
Recent Posts: Practical Blog
- Power View empowered practical Smart Client applications
- Tableau vs Qlikview and Tableau vs Spotfire
- Data, Story, View: Prototype and Update
- 2012 starts with Tableau 7.0
- SQL Server 2012 is good for Data Visualization
- Spotfire 4.0 is available
- Introduction of QlikView 11
- VisiCalc jubilee and history of Excel
- Data Visualization 2011: Omniscope 2.6
- Data Visualization 2011: Spotfire 3.3, Silver 2.0
- Data Visualization 2011: Tableau 6.1
- SQL Server 2012 is released for Preview